4 ms·

I'm not that familiar with the IoT ecosystem. What are the use cases for this standard and what are those use cases using instead of this standard at present? I

I'm not that familiar with the IoT ecosystem. What are the use cases for this standard and what are those use cases using instead of this standard at present? IoT implies connected to internet? So they have a full TLS stack? They send everything in the clear? .. They use TDES :)? Or they just use an non-standardized algorithm?

michaelt 4y ago
If you buy a $5 wifi-enabled lightbulb, there's a good chance it'll have an ESP32 (which can do most modern SSL) or an ESP8266 (which is short on memory, and so might use SSL with a preshared key, "TLS-PSK") On the other hand, if $5 devices seem a bit expensive to you, because you think $0.01 parcel labels will be part of the internet of things in the future, I suppose you might be interested in this new NIST algorithm?
- contact9879 4y ago
  I understand that, but these devices, how will they access the "internet"? They need to talk to a router or other device that is then connected to the internet. What protocol would they use to connect? Or is this for just "near-me area networks" that need to communicate with each other? I never really considered key fobs or pacemakers as IoT devices because they don't actually connect to the internet.
  - eternityforest 4y ago
    Pacemakers definitely need security though. Although I don't see why they can't use AES like everything else.
  - spelunker 4y ago
    Yes, some IoT devices communicate over WiFi, but others will talk to a gateway or hub over something else, such as BLE or Zigbee. I guess those could be the targets for this.
- nick__m 4y ago
  The ESP32-A1S is a fun toy to program with that lib https://github.com/pschatzmann/arduino-audio-tools https://github.com/pschatzmann/arduino-audio-tools on that cheap kit: https://docs.ai-thinker.com/en/esp32-audio-kit https://docs.ai-thinker.com/en/esp32-audio-kit
mmoskal 4y ago
For example LoRaWAN uses AES-CTR and AES-CMAC. BLE uses AES-CDC. Both are relatively easy to implement on Cortex M0 and up (which start at 10-30 cents).

michaelt 4y ago

If you buy a $5 wifi-enabled lightbulb, there's a good chance it'll have an ESP32 (which can do most modern SSL) or an ESP8266 (which is short on memory, and so might use SSL with a preshared key, "TLS-PSK") On the other hand, if $5 devices seem a bit expensive to you, because you think $0.01 parcel labels will be part of the internet of things in the future, I suppose you might be interested in this new NIST algorithm?

contact9879 4y ago
I understand that, but these devices, how will they access the "internet"? They need to talk to a router or other device that is then connected to the internet. What protocol would they use to connect? Or is this for just "near-me area networks" that need to communicate with each other? I never really considered key fobs or pacemakers as IoT devices because they don't actually connect to the internet.
- eternityforest 4y ago
  Pacemakers definitely need security though. Although I don't see why they can't use AES like everything else.
- spelunker 4y ago
  Yes, some IoT devices communicate over WiFi, but others will talk to a gateway or hub over something else, such as BLE or Zigbee. I guess those could be the targets for this.
nick__m 4y ago
The ESP32-A1S is a fun toy to program with that lib https://github.com/pschatzmann/arduino-audio-tools https://github.com/pschatzmann/arduino-audio-tools on that cheap kit: https://docs.ai-thinker.com/en/esp32-audio-kit https://docs.ai-thinker.com/en/esp32-audio-kit

mmoskal 4y ago

For example LoRaWAN uses AES-CTR and AES-CMAC. BLE uses AES-CDC. Both are relatively easy to implement on Cortex M0 and up (which start at 10-30 cents).