|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Thanks, Marek. My considerations:
1) I think we can live with SecureRandom.getInstance("SHA1PRNG") without calling setSeed.
2) We can use a non-0 value, no problem. Regarding the reuse of the previously created secureRandom, I think we can do that. Maybe we can do that inside the DefaultSecureRandomProvider, caching the last created secureRandom ?
3) Makes sense, but I don't see the need to force locking using volatile. Old threads can use an out-dated secureRandom. What is important is to get the secureRandom updated for future threads.