On 2011-07-26 13:30 PDT, Brian Smith wrote:
Mozilla would like to expose a secure PRNG (basically, a wrapper around
PK11_GenerateRandom) to JavaScript content:
https://bugzilla.mozilla.org/show_bug.cgi?id=440046
There is some agreement that we should maintain separate PRNG state for
each
On 07/26/2011 03:30 PM, Brian Smith wrote:
There is some agreement that we should maintain separate PRNG state
for each origin (roughly: domain name), and that all those states
should be separate from the PRNG state used internally.
PK11_GenerateRandom currently shares the PRNG state across all
On Tue, Jul 26, 2011 at 1:30 PM, Brian Smith bsm...@mozilla.com wrote:
Mozilla would like to expose a secure PRNG (basically, a wrapper around
PK11_GenerateRandom) to JavaScript content:
https://bugzilla.mozilla.org/show_bug.cgi?id=440046
There is some agreement that we should maintain
Using a separate PRNG state for each origin will ensure that entropy
is reused (since all of them will need to seed from the same master
PRNG). This is bad.
Not seeding them from the same master PRNG would reduce the entropy
available in each state. As was the case with Netscape Navigator in
Mozilla would like to expose a secure PRNG (basically, a wrapper around
PK11_GenerateRandom) to JavaScript content:
https://bugzilla.mozilla.org/show_bug.cgi?id=440046
There is some agreement that we should maintain separate PRNG state for each
origin (roughly: domain name), and that all those
5 matches
Mail list logo