upvote

points

by chipweinberger1 days ago |
comments
upvoteby rustyhancock1 days ago|
next
[-]
Sounds like that'll be a great read.

This is (literally) none of my business, but would you consider a cut down or basic open source version (hardware and software, with open software running in the proper hardware). Yes it'll be cloned by factories, and yes it will cut into sales no matter what proponents claim. (And yes it's probably more work than I imagine it is).

But also yes, it'll be genuine open hardware and might out live your interest in the project.

reply
upvoteby c0nsumer1 days ago|
parent|
[-]
Reading your comment it sounds like you're asking the author to do more work to potentially/likely undercut their own sales. They are already offering a quality device at a reasonable price without any untoward restrictions.

If you want a Free work-alike, why don't /you/ put in the work and make it happen?

reply
upvoteby amelius1 days ago|
prev|
next
[-]
How do you verify the ID? In the software? What if the software is hacked? I'm curious how this can be safe.
reply
upvoteby _fw1 days ago|
prev|
next
[-]
Please do! Trying to imagine how this works.
reply
upvoteby Teknomadix1 days ago|
prev|
next
[-]
Yes, please do!
reply
upvoteby DANmode1 days ago|
prev|
next
[-]
Please!
reply
upvoteby stavros1 days ago|
prev|
[-]
Please do, that'd be very interesting. I imagine it's doable to use random per-device I'd when you're hand-flashing, but probably harder on a huge production run.
reply
upvoteby swiftcoder1 days ago|
parent|
[-]
Almost all commercial devices need a unique ID, private key, etc burned in on the production line. For a big enough production run, you'd likely ship an HSM to the factory
reply
upvoteby chipweinberger1 days ago|
parent|
next
[-]
IMO it's better to ship preprogrammed ICs to the factory, so you can do your secure burning in-house.
reply
upvoteby swiftcoder1 days ago|
parent|
[-]
Depends on where the ICs originally come from. No point shipping your ICs from China -> US, flashing them, shipping them back US -> China for assembly, and then ship them China -> US again to sell
reply
upvoteby Teknomadix1 days ago|
parent|
next
[-]
Yet people do this all the time. Ask me how I know.
reply
upvoteby thenthenthen1 days ago|
parent|
prev|
[-]
Can reply to the reply below but yeah, i have done that, lol
reply
upvoteby Hackbraten1 days ago|
parent|
prev|
next
[-]
> For a big enough production run, you'd likely ship an HSM to the factory

I figure that the factory is exactly the adversary in the whole threat model? So why give them the keys to the castle so they can moonlight their own genuine batch?

reply
upvoteby NBJack1 days ago|
parent|
[-]
A few ways, if I understand them correctly. On-site people you employ (if you can afford it) auditing the process, connectivity to the HSM to record every key assigned (makes it easy to trace duplicated keys to their origin), and ideally assigning these keys at the very last possible step after the rest is assembled (to minimize 'defective' parts wandering off and being assembled elsewhere).
reply
upvoteby swiftcoder1 days ago|
parent|
[-]
Yeah, it's important that your own people are doing regular inspections of the production line, keys get burned at the final station (use temp keys for QA stages before that point), and you retain software control of the HSM.

You probably aren't going to do this whole rigmarole for small runs of devices like in the OP.

reply
upvoteby chrismorgan1 days ago|
parent|
prev|
[-]
> Almost all commercial devices need a unique ID, private key, etc

Serious question: why?

reply
upvoteby swiftcoder1 days ago|
parent|
[-]
You want a unique ID so that you can track which units are experiencing issues, you want private keys to be able to securely connect to your backend service and/or mobile companion app.

A local-only device with no telemetry can probably skip some of those

reply