RFR 8051408: JEP 273: DRBG-Based SecureRandom Implementations
weijun.wang at oracle.com
Tue Apr 26 06:25:08 UTC 2016
> On Apr 26, 2016, at 8:48 AM, Bradford Wetmore <bradford.wetmore at oracle.com> wrote:
> but the runtime "Health Testing" I was talking about is in the diagram of Section 7, and details in section 11.3:
I haven't touched this area yet.
If you think it's necessary, I would like to add the test inside the static <clinit> block of AbstractDrbg$SeederHolder. The test will be on Hash_DRBG/SHA-256 and whatever mech/algorithm defined by securerandom.drbg.config (They are the same by default). The test will be in the same thread (otherwise I don't know how to report an error). If it fails, a RuntimeException will be thrown.
I can extract the test from CAVP, instantiate + reseed + generate with both non-null personalization string and additional input, and PR on. It won't take long.
This is purely internal and automatic, maybe a new abstract method in AbstractDrbg is needed.
Can we do this after the JEP?
BTW, I probably will not be able to send out a new webrev today. Tomorrow is OK.
More information about the security-dev