Why are crypto/smartcard ICs (for example ATECC608) always so poorly documented / NDA-walled? The software/networking space is very open (TLS, IPSec, etc) and use of a proprietary cipher vs something like AES is massively frowned upon. So why is sec-by-obscurity OK in HW??
-
-
For example https://github.com/torvalds/linux/blob/master/drivers/crypto/atmel-ecc.c … is pretty sparsely commented, no reg definitions etc. Not sure if this is the official (lightly commented) source or redacted.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yes, I did read it. Source code with or without comments should compile exactly the same. So you are saying that comments are source code? My only point is that it is an interesting question.

-
It doesn't **matter** whether it compiles the same. Otherwise,it'd be open source if you deliver the LLVM IR assembly to your program.Compiles to the same machine bytecode (x86, ARM,…)! It's open source iff the code that you make public is the same code you work with. Full stop.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.