On Mon, 5 May 2025 08:50:07 GMT, Daniel Jeliński wrote:
> Well, technically the current 1ms takes into account both the client side and
> the server side of the handshake. Last time I checked, they were more or less
> evenly split. The 1ms slowdown will happen entirely on the server side, so
>
On Tue, 29 Apr 2025 21:51:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Tue, 29 Apr 2025 21:51:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Tue, 29 Apr 2025 21:51:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Tue, 29 Apr 2025 21:51:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
> The current key manager is SunX509, which is configured in the java.security.
> The SunX509 algorithm does not check the local certificate. The PKIX
> algorithm should be preferred now so that the default key manager could be
> more robust.
>
> Compatibility considerations:
>
> 1) Customers
On Tue, 29 Apr 2025 19:58:42 GMT, Sean Mullan wrote:
>> Artur Barashev has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Skip explicit KeyPair initialization and let the provider default set it
>
> test/jdk/javax/rmi/ssl/SSLSocketParameter
On Tue, 29 Apr 2025 18:51:58 GMT, Sean Mullan wrote:
>> Artur Barashev has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Skip explicit KeyPair initialization and let the provider default set it
>
> test/jdk/sun/security/tools/keytool/Print
On Thu, 24 Apr 2025 18:30:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Thu, 24 Apr 2025 18:30:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Thu, 24 Apr 2025 18:30:00 GMT, Artur Barashev wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be more
On Wed, 23 Apr 2025 23:28:29 GMT, Anthony Scarpino
wrote:
> Do we understand why this is so much slower? I wouldn't have thought extra
> checking would cause this big of a performance hit.
Yes, it looks that way. `SunX509` KeyManager is really simple, so adding
certificate validation can decr
> The current key manager is SunX509, which is configured in the java.security.
> The SunX509 algorithm does not check the local certificate. The PKIX
> algorithm should be preferred now so that the default key manager could be
> more robust.
>
> Compatibility considerations:
>
> 1) Customers
On Wed, 23 Apr 2025 17:54:38 GMT, Anthony Scarpino
wrote:
>> The current key manager is SunX509, which is configured in the
>> java.security. The SunX509 algorithm does not check the local certificate.
>> The PKIX algorithm should be preferred now so that the default key manager
>> could be m
On Fri, 18 Apr 2025 17:04:56 GMT, Artur Barashev wrote:
> The current key manager is SunX509, which is configured in the java.security.
> The SunX509 algorithm does not check of the local certificate. The PKIX
> algorithm should be preferred now so that the default key manager could be
> more
The current key manager is SunX509, which is configured in the java.security.
The SunX509 algorithm does not check of the local certificate. The PKIX
algorithm should be preferred now so that the default key manager could be more
robust.
-
Commit messages:
- Rework unit tests
- U
16 matches
Mail list logo
