On Thu, 27 Jun 2024 21:32:53 GMT, Valerie Peng wrote:
>>> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
>>> JDK 17 or 21 ?
>>
>> I am not sure, let me check and get back to you.
>
>> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
>> JD
On Thu, 27 Jun 2024 21:32:53 GMT, Valerie Peng wrote:
>>> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
>>> JDK 17 or 21 ?
>>
>> I am not sure, let me check and get back to you.
>
>> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
>> JD
On Fri, 14 Jun 2024 18:56:12 GMT, Valerie Peng wrote:
> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
> JDK 17 or 21 ?
Based on the feedback that I got, it should be ok to backport the PKCS11
configuration attribute, separate CSRs would be needed for that though.
On Tue, 16 Apr 2024 22:30:57 GMT, Valerie Peng wrote:
>> What about testing?
>
> @mcpowers I am about to leave for vacation. Will wait for your review and
> resume on this PR after I return. Thanks!
> UP @valeriepeng possible to backport PKCS11 configuration attribute part on
> JDK 17 or 21 ?
On Tue, 16 Apr 2024 22:30:57 GMT, Valerie Peng wrote:
>> What about testing?
>
> @mcpowers I am about to leave for vacation. Will wait for your review and
> resume on this PR after I return. Thanks!
UP @valeriepeng possible to backport PKCS11 configuration attribute part on
JDK 17 or 21 ?
--
On Tue, 16 Apr 2024 22:30:57 GMT, Valerie Peng wrote:
>> What about testing?
>
> @mcpowers I am about to leave for vacation. Will wait for your review and
> resume on this PR after I return. Thanks!
Many thanks @valeriepeng for this feature.
Possible to backport on JDK 17 or 21 ?
-
On Mon, 8 Apr 2024 19:33:25 GMT, Valerie Peng wrote:
>> Existing legacy mechanism check disables mechanism(s) when the support is
>> partial, e.g. supports decryption but not encryption, or supports
>> verification but not signing. Some mechanisms can be used for both
>> encryption/decryption
On Mon, 8 Apr 2024 19:33:25 GMT, Valerie Peng wrote:
>> Existing legacy mechanism check disables mechanism(s) when the support is
>> partial, e.g. supports decryption but not encryption, or supports
>> verification but not signing. Some mechanisms can be used for both
>> encryption/decryption
On Tue, 9 Apr 2024 18:37:44 GMT, Mark Powers wrote:
>> Valerie Peng has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Update to match CSR for disableLegacy -> allowLegacy name change
>
> What about testing?
@mcpowers I am about to leave f
On Tue, 9 Apr 2024 22:15:23 GMT, Valerie Peng wrote:
>> What about testing?
>
>> What about testing?
>
> I tested the change manually by changing some behavior to simulate the case.
> However, this cannot be done by regression test since NSS does not have
> legacy mechanisms.
> @valeriepeng c
On Tue, 9 Apr 2024 22:15:23 GMT, Valerie Peng wrote:
>> What about testing?
>
>> What about testing?
>
> I tested the change manually by changing some behavior to simulate the case.
> However, this cannot be done by regression test since NSS does not have
> legacy mechanisms.
@valeriepeng can
On Tue, 9 Apr 2024 18:34:52 GMT, Mark Powers wrote:
>> Valerie Peng has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Update to match CSR for disableLegacy -> allowLegacy name change
>
> src/jdk.crypto.cryptoki/share/classes/sun/security/p
On Tue, 9 Apr 2024 18:37:44 GMT, Mark Powers wrote:
> What about testing?
I tested the change manually by changing some behavior to simulate the case.
However, this cannot be done by regression test since NSS does not have legacy
mechanisms.
-
PR Comment: https://git.openjdk.org/
On Mon, 8 Apr 2024 19:33:25 GMT, Valerie Peng wrote:
>> Existing legacy mechanism check disables mechanism(s) when the support is
>> partial, e.g. supports decryption but not encryption, or supports
>> verification but not signing. Some mechanisms can be used for both
>> encryption/decryption
On Mon, 8 Apr 2024 19:33:25 GMT, Valerie Peng wrote:
>> Existing legacy mechanism check disables mechanism(s) when the support is
>> partial, e.g. supports decryption but not encryption, or supports
>> verification but not signing. Some mechanisms can be used for both
>> encryption/decryption
> Existing legacy mechanism check disables mechanism(s) when the support is
> partial, e.g. supports decryption but not encryption, or supports
> verification but not signing. Some mechanisms can be used for both
> encryption/decryption and sign/verify such as RSA related ones. If the
> particu
16 matches
Mail list logo
