[13] RFR JDK-8080462: Update SunPKCS11 provider with PKCS11 v2.40 support

Valerie Peng valerie.peng at oracle.com
Tue May 21 23:19:03 UTC 2019


I thought we always file CSR when updating the version of external 
standard, e.g. documenting the import aspect of JDK.

I'd love to close/withdraw the CSR if it's not needed.

Thanks,
Valerie
On 5/20/2019 12:11 PM, Sean Mullan wrote:
> On 5/17/19 3:56 PM, Valerie Peng wrote:
>>
>> Thanks Martin for helping me troubleshoot NSS side, I added PSS 
>> support into PKCS11 provider and added PSS-specific regression tests. 
>> Please find webrev updated as below:
>>
>> http://cr.openjdk.java.net/~valeriep/8080462/webrev.01/
>>
>> Can someone help review the CSR first as the approval may take a week 
>> or so.
>
> I am curious why a CSR is needed? This seems to be strictly an 
> implementation change with no compatibility effects.
>
> --Sean
>
>>
>> Thanks,
>> Valerie
>> On 4/12/2019 5:05 PM, Valerie Peng wrote:
>>>
>>> Anyone has time to review this? Besides the header files update, I 
>>> added support for AES/GCM/NoPadding support. Ran into some strange 
>>> NSS error with RSASSA-PSS signature mechanism, so I have not 
>>> included the PSS signature impl here.
>>>
>>> RFE: https://bugs.openjdk.java.net/browse/JDK-8080462
>>>
>>> Webrev: http://cr.openjdk.java.net/~valeriep/8080462/webrev.00/
>>>
>>> CSR: https://bugs.openjdk.java.net/browse/JDK-8221442
>>>
>>> Thanks,
>>> Valerie
>>>
>>>



More information about the security-dev mailing list