3 ms·

It is encrypted on the device. How are you going to get access to it?

deleted 7y ago
[deleted]
godelski 7y ago
My 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 ago
  If 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
    Okay I guess that makes sense. If I'm understanding you could get that information but you don't have access to the memory addresses unless you crack the firmware? Though in the case of Mozilla, wouldn't that be open so this wouldn't be that big of an issue?
    - blackflame7000 7y ago
      > you could get that information but you don't have access to the memory addresses unless you crack the firmware. Correct, from the moment the IoT device puts a packet on the line, it is encrypted end to end. This is a fundamental aspect of TLS to prevent snooping. To view unencrypted data, you have to access it prior to being sent out on the network which requires you to gain root privileges on the IoT device.
      - godelski 7y ago
        That makes sense. Thanks for the explanation!
- vineyardmike 7y ago
  The threat comes from closed-source devices. If these closed-source devices send un-encrypted data, you can MiTM these devices when they're on your network. But if they're encrypted, you're SOL.

deleted 7y ago

[deleted]

My 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 ago
If 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
  Okay I guess that makes sense. If I'm understanding you could get that information but you don't have access to the memory addresses unless you crack the firmware? Though in the case of Mozilla, wouldn't that be open so this wouldn't be that big of an issue?
  - blackflame7000 7y ago
    > you could get that information but you don't have access to the memory addresses unless you crack the firmware. Correct, from the moment the IoT device puts a packet on the line, it is encrypted end to end. This is a fundamental aspect of TLS to prevent snooping. To view unencrypted data, you have to access it prior to being sent out on the network which requires you to gain root privileges on the IoT device.
    - godelski 7y ago
      That makes sense. Thanks for the explanation!
vineyardmike 7y ago
The threat comes from closed-source devices. If these closed-source devices send un-encrypted data, you can MiTM these devices when they're on your network. But if they're encrypted, you're SOL.