Preventing IOT Edge Device Cloning
Posted3 months agoActive3 months ago
embedded.comTechstory
calmpositive
Debate
20/100
IOT SecurityDevice AuthenticationEdge Computing
Key topics
IOT Security
Device Authentication
Edge Computing
The article discusses methods to prevent IoT edge device cloning, and the discussion revolves around the challenges and potential solutions for securing IoT devices.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
29m
Peak period
2
0-1h
Avg / period
1.5
Key moments
- 01Story posted
Sep 23, 2025 at 5:34 PM EDT
3 months ago
Step 01 - 02First comment
Sep 23, 2025 at 6:04 PM EDT
29m after posting
Step 02 - 03Peak activity
2 comments in 0-1h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 24, 2025 at 4:17 AM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45353052Type: storyLast synced: 11/20/2025, 5:57:30 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
I couldn't find "actual sources", but one of their github repo has this: https://github.com/RealTimeLogic/BAS/blob/main/examples/Mako...
Which extracts to this .config file (looks like lua code, that creates a secret from PBKDF2 of... what? I couldn't find where secrets would come from here, but that repo obviously misses the interesting bindings; from the how it works link it looks like they're just hashing the SN to generate a pseudorandom key but I don't see why you couldn't just generate a key for neighboring devices by just faking the SN then...)
I guess the rest still provide value by transforming whatever random seed into a proper certificate though.
If they've captured the device, what if they don't clone it but use it directly instead?