Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

evilsocket.net

Post reply on HN
Print view View original

121–128 of 128 posts

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#121

Post by tyami94 »

evilsocket wrote: post #106
locknitpicker wrote: post #89

Earlier quoted context omitted.

> Nobody tell them about Linux! The blogger will blow a gasket when they discover that the likes of GitHub provides access to both installers and software. A hacker's candy store!

Do you people realize that there's a big difference between open source and proprietary technologies right?

Doesn't matter really, keeping blobs hidden doesn't actually do anything except make it slightly harder to analyze the software. Making all blobs easily and readily available is exactly what I want the vendor to do. Black boxes don't make things secure.

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#122

Post by tyami94 »

lmz wrote: post #118
locknitpicker wrote: post #104

Earlier quoted context omitted.

> Maybe listing shouldn't be enabled even if all the files are public. I don't see why. Support for firmware upgrades literally involve querying available packages and downloading the latest ones (i.e., apply upgrades). Either you use something like the S3 interface, or you waste your time implementing a clone of what S3 already supports. Sometimes simple is good, specially when critics can't even provide any concret…

It's not a necessary interface. Do the clients actually use S3 listing to determine what the latest firmware is? Personally I would put a service in the middle that takes in the model number, region, etc and then returned the most recent firmware URL. There's no reason to have historical versions be easily listable by curious people.

Why not? The firmware was already public at one point. If people are analyzing your app to find an S3 bucket full of firmware, I'd assume they'd have a pretty good reason to go through the effort.

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#123

Post by evilsocket »

tyami94 wrote: post #121
evilsocket wrote: post #106

Earlier quoted context omitted.

Do you people realize that there's a big difference between open source and proprietary technologies right?

Doesn't matter really, keeping blobs hidden doesn't actually do anything except make it slightly harder to analyze the software. Making all blobs easily and readily available is exactly what I want the vendor to do. Black boxes don't make things secure.

Agreed 100%, never said the opposite

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#124

Post by tguvot »

justsomehnguy wrote: post #119
tguvot wrote: post #117

Earlier quoted context omitted.

yes for example https://newsroom.axis.com/en-us/press-release/macsec-zero-tr...

That's great. Now we need to get an enterprise grade switch - doubt Cisco would add macsec into SOHO gear. Along with enterprise grade intercoms, cameras, doorbells... And beloved by many Unifi is out of question - they still can't bake IPv6 support. So looks like it's feasible but the cost wouldn't be good. ADD: also read this article: https://news.ycombinator.com/item?id=41531699

i well familiar with macsec. we use it between datacenters and for aws directlink. it de-facto standard for this kind of stuff. i even worked on hardware that provided macsec support

a couple of years ago I tried to use it inside datacenter during fedramp implementation. it crashed and burned for a couple of reasons:

- linux wpa_supplicant was crashing during session establishment

- switch had a limit on number of macsec session per port

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#125

Post by plugger »

locknitpicker wrote: post #89
hdgvhicv wrote: post #59

Earlier quoted context omitted.

> I found out that TP-Link have their entire firmware repository in an open S3 bucket. Nobody tell them about Linux!

> Nobody tell them about Linux! The blogger will blow a gasket when they discover that the likes of GitHub provides access to both installers and software. A hacker's candy store!

This blogger is the author of bettercap, safe to say they're fairly across Github

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#126

Post by alexfoo »

justsomehnguy wrote: post #119
tguvot wrote: post #117

Earlier quoted context omitted.

yes for example https://newsroom.axis.com/en-us/press-release/macsec-zero-tr...

That's great. Now we need to get an enterprise grade switch - doubt Cisco would add macsec into SOHO gear. Along with enterprise grade intercoms, cameras, doorbells... And beloved by many Unifi is out of question - they still can't bake IPv6 support. So looks like it's feasible but the cost wouldn't be good. ADD: also read this article: https://news.ycombinator.com/item?id=41531699

Looks like some Ubiquiti UniFi switches (definitely SOHO) support 802.1x

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#127

Post by justsomehnguy »

alexfoo wrote: post #126
justsomehnguy wrote: post #119

Earlier quoted context omitted.

That's great. Now we need to get an enterprise grade switch - doubt Cisco would add macsec into SOHO gear. Along with enterprise grade intercoms, cameras, doorbells... And beloved by many Unifi is out of question - they still can't bake IPv6 support. So looks like it's feasible but the cost wouldn't be good. ADD: also read this article: https://news.ycombinator.com/item?id=41531699

Looks like some Ubiquiti UniFi switches (definitely SOHO) support 802.1x

802.1x != MACSEC

Re: TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

#128

Post by kapad »

syntaxing wrote: post #29

This is why all my cameras internal or external live on an isolated VLAN with no internet access. It’s nice because HomeKit can still talk to them and I can see it online or locally without an additional app even though the camera themselves has no internet access .

How do you set this up? (TL;DR version?)
Post reply on HN