3 ms·
> * Modulo simplifying assumptions. Do you mean there are any special cases situations where entropy is extremely low? Just after reboot? Just after first inst
by im3w1l 11y ago
> * Modulo simplifying assumptions.
Do you mean there are any special cases situations where entropy is extremely low? Just after reboot? Just after first install? Just after booting a VM from an image (where the "entropy" could be public knowledge)? Container?
- deleted 11y ago[deleted]
- mindslight 11y agoI was referring to assumptions that let one equate breaking urandom with breaking arbitrary cryptosystems in other ways. examples: 1. Breaking urandom's construction is much less likely than breaking a less-trodden hardware device. 2. If hashes in general are broken, then any crypto of interest is also broken (counter example: non-complexity based crypto like a one-time pad (note: Do NOT construe this as any sort of practical endorsement of "one time pads". If you do not understand the concept of malleability, then forget this entire comment exists and go read up on that instead!)). 3. Backdooring RDRAND is equivalent to backdooring the entire CPU (counter: a model of auditability that constrains the complexity of a backdoor) These assumptions are mostly reasonable, but they are assumptions nonetheless. Embedded systems do suffer from a demonstrable lack of entropy. Studying techniques for hardware entropy collection is interesting in its own right, which is why it's disappointing that this page seems more focused on productizing their device as a black box USB stick rather than concentrating on open review.
- amirmc 11y agoThere's a nice post about entropy in such (virtualised) environments, with specific regard to unikernels. https://mirage.io/blog/mirage-entropy https://mirage.io/blog/mirage-entropy