On Tue, 26 Mar 2024 06:00:33 GMT, Hai-May Chao wrote:
>> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
>> ServerHello message and ultimately calls the
>> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the
>> private key from the keystore,
On Wed, 27 Mar 2024 08:15:08 GMT, Hai-May Chao wrote:
> I ran the benchmark to measure the time needed to build a TLS context using
> PKIX KeyManager (with protocols "TLSv1.2" and "TLS”) before and after the
> changes to X509KeyManagerImpl.java. Here are the results:
>
> Without changes:
On Tue, 26 Mar 2024 06:00:33 GMT, Hai-May Chao wrote:
>> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
>> ServerHello message and ultimately calls the
>> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the
>> private key from the keystore,
On Tue, 26 Mar 2024 06:00:33 GMT, Hai-May Chao wrote:
>> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
>> ServerHello message and ultimately calls the
>> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the
>> private key from the keystore,
On Tue, 26 Mar 2024 06:00:33 GMT, Hai-May Chao wrote:
>> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
>> ServerHello message and ultimately calls the
>> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the
>> private key from the keystore,
On Tue, 26 Mar 2024 06:00:33 GMT, Hai-May Chao wrote:
>> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
>> ServerHello message and ultimately calls the
>> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the
>> private key from the keystore,
> For the PKIX KeyManager and PKCS12 Keystore, when the TLS server sends the
> ServerHello message and ultimately calls the
> X509KeyManagerImpl.chooseEngineServerAlias() method, it retrieves the private
> key from the keystore, decrypts it, and caches both the key and its
> certificate. This