←back to thread

314 points walterbell | 2 comments | | HN request time: 0.494s | source
1. mrlambchop ◴[] No.43690261[source]
Great article - enjoyed it a lot!

re: the notes on the use of the device keys (stored in the K/V store), assuming that they are per device would seem the most obvious vs that they are global. Global keys would be written in the main app body in my experience, not the KV store (but that doesn't mean people have not done unusual things here of course!).

I also want to share some feedback on the complexity of managing per device keys these days and the risks - there are lots of easy to use tools that per device keys like this much simpler to do in 2025 than 2015 and cloud platforms that take in CSV files and return very similar messages... Typically a security model for a device such as an air purifier can be easily defined as not having device encryption enabled if it has per-device keys on as the impact of breaching a single device remains compartmentalized to a single edge component and in this case, just a purifier (vs a car or something that explodes!). Not that I agree with this, but corporate security can! Device encryption causes lots of problems in factories that are often best 'ignored' if the product can afford it.

Per another comment, god bless ESP32 developers once the EU rule kicks in in August... !

replies(1): >>43731190 #
2. flakespancakes ◴[] No.43731190[source]
Oh oh - what EU rule?