The algorithm name decomposer implementation for algorithm restrictions
depends on the pattern:
with
Using the same "encryption" name for signature and PKCS#1 could be
easier for applications if there is a need to decompose the algorithms.
Xuelei
On 4/16/2018 11:40 AM, Sean Mullan wrote:
Please take a review of this fix:
webrev: http://cr.openjdk.java.net/~weijun/8201627/webrev.00/
CSR: https://bugs.openjdk.java.net/browse/JDK-8201814
Basically we fix some bugs and introduce a system property so we can interop
with everyone.
Thanks
Max
On 4/18/18 12:52 PM, Xuelei Fan wrote:
The algorithm name decomposer implementation for algorithm restrictions
depends on the pattern:
with
Using the same "encryption" name for signature and PKCS#1 could be
easier for applications if there is a need to decompose the algorithms.
Hmm, so
On 4/18/2018 11:25 AM, Sean Mullan wrote:
On 4/18/18 12:52 PM, Xuelei Fan wrote:
The algorithm name decomposer implementation for algorithm
restrictions depends on the pattern:
with
Using the same "encryption" name for signature and PKCS#1 could be
easier for applications if there is a ne
Hi,
We are hitting the scalability problem of the SSL session cache in
production that JDK-8186628 is addressing. I see that JDK-8186628 has not
been updated since Nov'17, so I just wanted to get information about what
the current plans are regarding that issue.
Thanks,
Nezih
Please take a review at
https://bugs.openjdk.java.net/browse/JDK-8201906
OpenJDK will switch from a home-grown list to Mozilla PSL. This is a behavior
change, therefore a CSR.
Thanks
Max
