6 ms·
This the closest we have so far to an answer to the point raised in the IETF 105 Technical Plenary a few days ago. Encrypting everything means that IoT devices
by tialaramex 7y ago
This the closest we have so far to an answer to the point raised in the IETF 105 Technical Plenary a few days ago.
Encrypting everything means that IoT devices represent an unknown threat - your "smart" TV connects to Sourceforge and downloads... something every week. What for? Your "smart" thermostat calls the IP of the vendor, maybe to get firmware updates, but it also calls the Disney corporation - what for? You can't snoop any of this because it's using encryption with pinned keys, so MITM doesn't work. Obviously hardcore reverse engineering is possible, but it's extremely expensive. So in practice it won't get done.
But, if we can popularize a safe option, we can just flag all the unsafe approaches that are popular today. We can teach vendors that this is a bad idea and they shouldn't do it, and (cross fingers) it might go away, like X-ray shoe sizing.
- eb0la 7y ago> if we can popularize a safe option, we can just flag all the unsafe approaches I am not a lawyer, but I think under european privacy laws those approaches are probably ilegal, too. If some manufacturer (probably chinese) wants to grab data from people in Europe, they must comply with EU laws even if they don't have an office in the EU. Not beign able to sell to a huge market is probably a better tactique, but not the only one to use.
- tialaramex 7y agoOne of the things mentioned in that Plenary is that partial technical solutions embolden regulators and legislators. We don't have to make everything bad impossible. We can make it a bit harder to do the wrong thing, and then the regulator says "Hey, do the easy thing these nerds recommend or else if we find you did the wrong thing you're in bad trouble".
- sp332 7y agoIf you can't tell what data is being sent or retrieved, how will you prosecute them?
- tialaramex 7y agoI can't tell what my 2028 model Foo Corp. Smart TV is sending to the HBO servers or why, it's technically impossible thanks to cryptography. But a Federal Prosecutor can tell a judge these are the only Smart TVs that do that, and he thinks it's because they're violating the Tialaramex No Snooping Act of 2025, so he wants a warrant to see what HBO receives. The warrant doesn't magically decrypt the packets - but refusing to obey the warrant is contempt of court, for which you can go to jail. An HBO employee shows the Prosecutor their database labelled "snooping" full of data from Foo Corp TVs that sure enough violates the No Snooping Act.
- sp332 7y agoDon't you need probable cause to get a warrant? This might be different in Europe actually... but it seems a bit thin.
- FeepingCreature 7y agoIn Europe, with the GDPR, you can just ask the company what they have on you.
- gcbw2 7y ago"Hey company in shenzen that i suspect is a shady front to illegal data mining business, do you have any data on me? i'm john doe, living at 123 naive st #42, phone number 555-555-555, national registry number 1234556. You can reply to me on this same email address. thank you. PS: maybe i filled this in an webform, so please do not attach this new info to all the traffic/behaviour you previously collected from your TV on this same IP address"
- tialaramex 7y agoSure, so it depends on circumstances in the broader society. The judge needs to be convinced that on balance it's more likely the case that the prosecutor is right than not. That's all probable cause is. In today's IoT world where basically everybody does all this potentially shady stuff sending encrypted data to who knows where, and with no legislation on the books saying they mustn't, you would not get anywhere trying to obtain a warrant. But if things like WebThings Gateway were to make that unusual, so that as I said there aren't other Smart TVs sending mysterious stuff directly to HBO - that changes the balance of probabilities, and it also changes the incentive to regulate / legislate behaviours that are now less common and still undesirable so that what they're doing isn't just immoral it's illegal too. Circumstances change. In 1975 the idea that you shouldn't smoke cigarettes inside a train, deep under the ground, in a crowded city, was a bit weird. By 1983 it was illegal in London. In 1985 somebody who'd cut a few corners and was lighting a cigarette on the escalator out of the Underground caused a fire in which a lot of people died (a lot of other things went wrong, but none of them would have mattered if not for the cigarette). Today when we're trying to explain that fire to children it doesn't make a lot of sense to them. They don't remember it ever being legal to smoke cigarettes inside a building - it smells bad and looks obviously dangerous - why would somebody be doing it not just inside a building but so deep underground?
- doctorpangloss 7y ago> You can't snoop any of this... Obviously hardcore reverse engineering is possible, but it's extremely expensive The path to the platform you want looks like the iOS App Store.
- degenerate 7y agoI was fascinated by your X-ray example. Here's a link for others: https://en.wikipedia.org/wiki/Shoe-fitting_fluoroscope https://en.wikipedia.org/wiki/Shoe-fitting_fluoroscope
- gcbw2 7y agohere's one more relevant today https://en.wikipedia.org/wiki/Backscatter_X-ray https://en.wikipedia.org/wiki/Backscatter_X-ray
- Shorn 7y agoGoddammit. The comments are why I browse HN on a daily basis, but sometimes you folks are worse than Wikipedia. I know I shouldn't click that link. /me grumpily clicks link
- ryacko 7y agoNULL ciphersuites exist for TLS, but knowing what data is sent is meaningless. You find out after you purchase the device, are you going to send it back? What if data collection policies change? Besides, SSH begins with encryption, how do you audit an SSH connection?
- godelski 7y agoI'm no security expert, and maybe one can explain this to me, but why can't we just inspect the data before it is encrypted? Like isn't it gathered in some way, encrypted, then sent? And on the receiving end it has to decrypt, so we look at that (naively what files change). Unless this is all stored as encrypted I don't see why you can't do this. I mean this should prevent mitm attacks but also let those controlling devices inspect packets. Right? Or am I missing something (if so I'm legitimately interested. Lots of this stuff just seems like black box to me, and I'm sure others)
- garmaine 7y agoIt is encrypted on the device. How are you going to get access to it?
- deleted 7y ago[deleted]
- godelski 7y agoMy confusion is that I think there has to be a command that is encryptThisDataToBeSent(data). Can't you just look at data? Before it is encrypted? Or is data encrypted at all times? But if that's true, then the difference of sending encrypted data is kinda moot.
- ripdog 7y agoIf you can root the device and replace the firmware, sure. Or do extremely difficult hardmodding to tap the data buses, perhaps. But both of those approaches are very difficult and resource-intensive. The first requires many, many hours of reverse engineering to find a security hole which allows you to write unsigned firmware to the device (or find a way to sign your own firmware and then upload it), then hack the firmware to do your snooping (good luck if the firmware updates are encrypted!). The second is so fiddly and awkward, I've never heard of anyone actually doing it.
- godelski 7y ago
- downrightmike 7y ago"We can teach vendors that this is a bad idea and they shouldn't do it, and (cross fingers) it might go away" If Mozilla puts the work in and the vendors have to do is copy it, then they'll copy it like everything else they use. FLOSS makes the net go round.