[Bug crypto/27111] SecureRandom isn't seeded on creation

[csm at gnu dot org]

------- Comment #2 from csm at gnu dot org  2006-04-11 20:54 -------
The situation is a bit different: according to the spec, we need to seed the
instance if it is not seeded by the caller. To quote the Javadoc for the
default SecureRandom constructor:

"Note that this instance of SecureRandom has not been seeded. A call to the
setSeed method will seed the SecureRandom object. If a call is not made to
setSeed, the first call to the nextBytes method will force the SecureRandom
object to seed itself."

The same is true for SecureRandom objects created through the `getInstance'
factory methods.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27111