3 ms·
Really? I would have expected better from you for your reputation. :-) Read carefully what I said. Explained more clearly, XORing is at worst a ceiling functio
by hueving 13y ago
Really? I would have expected better from you for your reputation. :-)
Read carefully what I said. Explained more clearly, XORing is at worst a ceiling function of the entropy of two random sources. If it weren't, that would imply one-time pad is insecure.
- tptacek 13y agoI was reacting to "blocking function bound by available entropy".
- hueving 13y agoIf you care about having good random bytes, you should call a blocking random function (i.e it doesn't return random data until enough entropy is collected)(e.g./dev/urandom). If you don't care about security, you can certainly call one that always returns using a PRNG (/dev/random). However, with it being based on a much smaller random seed, using it to generate keys is massively reducing the key space an attacker would need to search for discovery. In summary, reading from /dev/random is a blocking function bound by available entropy and it's more secure than it's /dev/urandom counterpart that is not bound by entropy. I'm not sure what your problem is there. Care to elaborate?