On Wed, 23 Mar 2022 21:59:02 GMT, Valerie Peng wrote:
>> I see.
>>
>> Would you mind add a comment about the provider loading impact, just in case
>> someone else have similar questions in the future?
>
> Sure, I can do that. Will add a comment about this.
Thank you. I have no more comment
On Wed, 23 Mar 2022 21:51:51 GMT, Xue-Lei Andrew Fan wrote:
>> My very first prototype is to implement the AES keysize calculation as you
>> commented, i.e. in the static block and use an int for DEF_AES_KEY_SIZE.
>> However, it is later discovered through testing that this leads to deadlocks
On Wed, 23 Mar 2022 20:45:22 GMT, Valerie Peng wrote:
>> src/java.base/share/classes/sun/security/util/SecurityProviderConstants.java
>> line 129:
>>
>>> 127: return currVal;
>>> 128: }
>>> 129:
>>
>> I'm not very sure of this method. Is it performance friendly if making the
>>
On Wed, 23 Mar 2022 04:46:48 GMT, Xue-Lei Andrew Fan wrote:
>> Valerie Peng has updated the pull request incrementally with one additional
>> commit since the last revision:
>>
>> Minor code refactoring
>
> src/java.base/share/classes/sun/security/util/SecurityProviderConstants.java
> line
On Tue, 22 Mar 2022 21:25:28 GMT, Valerie Peng wrote:
>> It's been several years since we increased the default key sizes. Before
>> shifting to PQC, NSA replaced its Suite B cryptography recommendations with
>> the Commercial National Security Algorithm Suite which suggests:
>>
>> - SHA-384
On Tue, 22 Mar 2022 21:25:28 GMT, Valerie Peng wrote:
>> It's been several years since we increased the default key sizes. Before
>> shifting to PQC, NSA replaced its Suite B cryptography recommendations with
>> the Commercial National Security Algorithm Suite which suggests:
>>
>> - SHA-384
> It's been several years since we increased the default key sizes. Before
> shifting to PQC, NSA replaced its Suite B cryptography recommendations with
> the Commercial National Security Algorithm Suite which suggests:
>
> - SHA-384 for secure hashing
> - AES-256 for symmetric encryption
> -
