JDK-8024253 : ThreadLocal random can use SecureRandom for the initial seed
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.concurrent
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2013-09-04
- Updated: 2017-05-17
- Resolved: 2013-09-20
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8 b110Fixed  |
Related Reports
|
Blocks :
|
Description
SplittableRandom supports the following:
* in security-sensitive applications. Additionally,
* default-constructed instances do not use a cryptographically random
* seed unless the {@linkplain System#getProperty system property}
* {@code java.util.secureRandomSeed} is set to {@code true}.
ThreadLocalRandom can do the same, but requires JDK-8024009 to be fixed first.