> In addition to the goals, scope, motivation, specification and requirement
> notes in [JDK-8315487](https://bugs.openjdk.org/browse/JDK-8315487), we would
> like to describe the most relevant decisions taken during the implementation
> of this enhancement. These notes are organized by feature,
> Many crypto service classes require a `SecureRandom` object at
> initialization. This test goes through each of them and calculates (generate,
> encrypt, sign,...) twice with the same `SecureRandom` object and ensures the
> output is the same.
Weijun Wang has updated the pull request incremen
On Thu, 8 Feb 2024 20:53:03 GMT, Kevin Driver wrote:
>> Many crypto service classes require a `SecureRandom` object at
>> initialization. This test goes through each of them and calculates
>> (generate, encrypt, sign,...) twice with the same `SecureRandom` object and
>> ensures the output is t
On Thu, 8 Feb 2024 16:34:00 GMT, Weijun Wang wrote:
> Many crypto service classes require a `SecureRandom` object at
> initialization. This test goes through each of them and calculates (generate,
> encrypt, sign,...) twice with the same `SecureRandom` object and ensures the
> output is the sa
Many crypto service classes require a `SecureRandom` object at initialization.
This test goes through each of them and calculates (generate, encrypt,
sign,...) twice with the same `SecureRandom` object and ensures the output is
the same.
-
Commit messages:
- initial change
Change
On Wed, 7 Feb 2024 15:27:46 GMT, Prajwal Kumaraswamy
wrote:
>> src/java.base/share/classes/sun/security/ssl/X509Authentication.java line
>> 205:
>>
>>> 203: X509ExtendedKeyManager km = chc.sslContext.getX509KeyManager();
>>> 204: if (SSLLogger.isOn && SSLLogger.isOn("ssl")) {
>
> During the time of server certificate validation, users have the flexibility
> to use a custom X509 Key Manager implementation by extending
> "X509ExtendedKeyManager.".
> In such cases, printing the class name in X509Authentication.java will be
> helpful to trace any failure of the SSL connect
