3 ms·
OK, but the way you interpreted my question was not the way I meant it. You had already made it clear that you trust vendors. And that's fine. It's not unrea
by lisper 10y ago
OK, but the way you interpreted my question was not the way I meant it. You had already made it clear that you trust vendors. And that's fine. It's not unreasonable to trust a vendor. You have to trust someone.
When I asked, "Are you sure..." I did not mean "you, Thomas Ptacek." I didn't even mean, "You, Hanno Böck" even though he is the one I was actually responding to. I meant, "You, some hypothetical person in a hypothetical scenario", specifically, a scenario where you (the hypothetical person, not you, Thomas Ptacek) are "approaching this level of paranoia", i.e. where (hypothetical) you believe that a compromised CSPRNG is a possibility you need to seriously consider for whatever reason. How can that person be confident that they can trust OpenBSD?
In case you are tempted to take another whack at an answer, let me stipulate that I am assuming that this hypothetical person to whom the question is being addressed is reasonably technically competent but not a crypto expert. In particular, my hypothetical person does not know who Thomas Ptacek is, and so has no reason to lend any particular credence to his assessment of the situation in the absence of other evidence or arguments.
- tptacek 10y agoYou asked whether the LRNG had been competently audited. It has been, by multiple groups. If you'd asked me whether the XNU kernel RNG has been audited, I would give the same answer. Different groups, of course. I don't see how these answers depend on who asked the question. It could be me asking, it could be Trevor Perrin asking, it could be Theodore T'so. The scrutiny received by both of these CSPRNGs would be the same. If you believe your personal machine has been so completely compromised that the code for your kernel CSPRNG differs materially from the current reference code that has been reviewed, you have bigger problems than your CSPRNG. Whether you have those problems or not, writing an ad hoc userland CSPRNG is unlikely to mitigate any problem, but is very likely to cause new ones. Practically all major crypto randomness vulnerabilities are caused by userland RNGs. The funny thing about this thread is that I thought I'd entered it by agreeing with you! Certainly, I think this RFC is pretty dumb.
- lisper 10y ago> You asked whether the LRNG had been competently audited. No, that's not what I asked. I asked how can one know whether or not it has been competently audited. Those are two very different questions. (An illustrative analogy: "Does the Higgs boson exist?" and "How do we know that the Higgs boson exists?" are two very different questions. The answer to the first question is "yes". The answer to the second question is a very long story.) > It has been, by multiple groups. Yes, I know. Again, that's not what I asked. What I asked was: how can someone who doesn't know who you are, and hence is not willing to take your word for it, convince themselves that this statement is true? > I don't see how these answers depend on who asked the question. Do you understand it now? > I thought I'd entered it by agreeing with you! And I'm pretty sure you still do :-)
- tptacek 10y agoMy suggestion is, if you're wondering whether the LRNG has been competently audited, that you ask someone in a position to know. There are lots of those people.
- lisper 10y agoOK, but that only works for open-source OSs, not commercial ones. Also, it really helps to have a certain amount of crypto-savvy to be able to distinguish a competent consultant from a snake-oil salesman. BTW, /dev/urandom on OS X may be random, but it is ridiculously slow: ``` time head -100000 /dev/urandom > /dev/null real 0m1.832s user 0m0.015s sys 0m1.817s ``` So there's another reason someone might want to implement their own CSPRNG.
- tptacek 10y agoI don't understand. For closed-source operating systems, why can't you do the exact same thing? Just ask people who might know. You won't get specific answers, because that kind of work happens under NDA, but you'll get the answer you need, which is in this case "yes, they've been reviewed, by experts". Take yes for an answer!