> This update is to support signature schemes customization for individual
> (D)TLS connection. Please review the CSR as well:
> CSR: https://bugs.openjdk.java.net/browse/JDK-8280495
> RFE: https://bugs.openjdk.java.net/browse/JDK-8280494
Xue-Lei Andrew Fan has updated the pull request increment
On Sun, 30 Jan 2022 03:08:22 GMT, Bernd wrote:
>> Yes, it does. Do you like to use a for-loop, without new object allocation?
>
> Yes, static helper
Thanks for confirm. Updated to use a static helper method.
-
PR: https://git.openjdk.java.net/jdk/pull/7252
In the JSSE specification, the reference to "Java Security Standard Algorithm
Names" specification is documented as "Java Cryptography Architecture Standard
Algorithm Name Documentation". As should be corrected.
-
Commit messages:
- 8280949: Correct the references for the Java Sec
> In the JSSE specification, the reference to "Java Security Standard Algorithm
> Names" specification is documented as "Java Cryptography Architecture
> Standard Algorithm Name Documentation". As should be corrected.
Xue-Lei Andrew Fan has updated the pull request incrementally with one
addit
On Mon, 31 Jan 2022 16:01:56 GMT, Xue-Lei Andrew Fan wrote:
>> In the JSSE specification, the reference to "Java Security Standard
>> Algorithm Names" specification is documented as "Java Cryptography
>> Architecture Standard Algorithm Name Documentation". As should be corrected.
>
> Xue-Lei A
Method `Provider.getKey` was added in
[JDK-8276660](https://bugs.openjdk.java.net/browse/JDK-8276660). It was unused
since introduction.
Method `EngineDescription.getConstructorParameterClass()` and field
`EngineDescription.constructorParameterClass` is unused since
[JDK-7191662](https://bugs.o
> In the JSSE specification, the reference to "Java Security Standard Algorithm
> Names" specification is documented as "Java Cryptography Architecture
> Standard Algorithm Name Documentation". As should be corrected.
Xue-Lei Andrew Fan has updated the pull request incrementally with one
addit
On Mon, 31 Jan 2022 16:39:34 GMT, Sean Mullan wrote:
> Please capitalize "specification" (i.e. "Specification") to be consistent
> with other references in the javadoc. Looks good otherwise.
OK. Just curious, why we want to use capitalized "specification"? This word
"specification" is not a
On Mon, 31 Jan 2022 19:19:28 GMT, Xue-Lei Andrew Fan wrote:
> > Please capitalize "specification" (i.e. "Specification") to be consistent
> > with other references in the javadoc. Looks good otherwise.
>
> OK. Just curious, why we want to use capitalized "specification"? This word
> "specifica
On Mon, 31 Jan 2022 20:05:45 GMT, Sean Mullan wrote:
> > > Please capitalize "specification" (i.e. "Specification") to be consistent
> > > with other references in the javadoc. Looks good otherwise.
> >
> >
> > OK. Just curious, why we want to use capitalized "specification"? This word
> > "s
> This update is to support signature schemes customization for individual
> (D)TLS connection. Please review the CSR as well:
> CSR: https://bugs.openjdk.java.net/browse/JDK-8280495
> RFE: https://bugs.openjdk.java.net/browse/JDK-8280494
Xue-Lei Andrew Fan has updated the pull request increment
On Mon, 31 Jan 2022 15:37:38 GMT, Xue-Lei Andrew Fan wrote:
> In the JSSE specification, the reference to "Java Security Standard Algorithm
> Names" specification is documented as "Java Cryptography Architecture
> Standard Algorithm Name Documentation". As should be corrected.
This pull reque
On Wed, 15 Dec 2021 09:20:38 GMT, Boris Ulasevich
wrote:
> Background
>
> The goal is to improve SHA3 implementation performance as it runs up to two
> times slower than native (OpenSSL, measured on AMD64 and AArch6464)
> implementation. Some hardware provides SHA3 accelerators, but most (AMD
On Mon, 31 Jan 2022 20:24:47 GMT, Xue-Lei Andrew Fan wrote:
>> This update is to support signature schemes customization for individual
>> (D)TLS connection. Please review the CSR as well:
>> CSR: https://bugs.openjdk.java.net/browse/JDK-8280495
>> RFE: https://bugs.openjdk.java.net/browse/JDK-
On Sat, 29 Jan 2022 05:26:33 GMT, Xue-Lei Andrew Fan wrote:
>> src/java.base/share/classes/javax/net/ssl/SSLParameters.java line 94:
>>
>>> 92:
>>> 93: /**
>>> 94: * Constructs SSLParameters.
>>
>> Would it be useful to add another ctor that takes a signature schemes array
>> paramet
On Thu, 20 Jan 2022 18:25:48 GMT, Andrey Turbanov wrote:
> Method `Provider.getKey` was added in
> [JDK-8276660](https://bugs.openjdk.java.net/browse/JDK-8276660). It was
> unused since introduction.
> Method `EngineDescription.getConstructorParameterClass()` and field
> `EngineDescription.con
On Fri, 28 Jan 2022 16:58:55 GMT, Michael McMahon wrote:
>> Hi,
>>
>> This change adds Channel Binding Token (CBT) support to HTTPS
>> (java.net.HttpsURLConnection) when used with the Negotiate (SPNEGO,
>> Kerberos) authentication scheme. When enabled, the implementation
>> preemptively inclu
> This update is to support signature schemes customization for individual
> (D)TLS connection. Please review the CSR as well:
> CSR: https://bugs.openjdk.java.net/browse/JDK-8280495
> RFE: https://bugs.openjdk.java.net/browse/JDK-8280494
Xue-Lei Andrew Fan has updated the pull request increment
On Mon, 31 Jan 2022 21:26:46 GMT, Sean Mullan wrote:
>> As there is increasing number of SSL parameters, applications may just use
>> the constructor with no argument, and use the set methods individually.
>
> Ok. You should specify what the default value of the signature schemes
> parameter is
On Mon, 31 Jan 2022 21:55:18 GMT, Sean Mullan wrote:
>> Xue-Lei Andrew Fan has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Rollback to use captialized S
>
> src/java.base/share/classes/javax/net/ssl/SSLParameters.java line 727:
>
>> 725
On Thu, 13 Jan 2022 12:10:11 GMT, Michael McMahon wrote:
> Hi,
>
> This change adds Channel Binding Token (CBT) support to HTTPS
> (java.net.HttpsURLConnection) when used with the Negotiate (SPNEGO, Kerberos)
> authentication scheme. When enabled, the implementation preemptively includes
> a
21 matches
Mail list logo