it’s hilarious how a lot of HWWs use SEs that are broken, are uncertified or made for cheap IoT devices (often all of these)… or none at all

if your device is stateful a quality SE is a must, it’s only a few dollars more

Reply to this note

Please Login to reply.

Discussion

How do we know if it's a cheap one?

ATECC508A, ATECC608A and ATECC608B are all vulnerable to fault injection

And who currently use these?

Fuck shit biscuits lmfao

Whoa!!!!!!!

That's really interesting. Thank you.

On an other note, do you know what this means? I've always wondered what kind of government deal was taken by coldcard with the government to protect others from selling their code.

(I mean the MIT + CC)

It doesn’t meet the definition of open source (commercial use is not permitted for Coldcard firmware). The term source available is used instead

I understand that but I was asking more precisely which understand that but I was asking more precisely what this acronym meant. I tought it could give me a clearer picture of the specific laws that are used.

MIT+CC is MIT license with Commons Clause

Those are secp256r1 not k1. What role do they play in Bitcoin?

Where are the details on that exploit?

Do you have a list of HWWs with shitty / no SEs?

all of them except ledger i suppose...

Would you recommend any particular HWW?