Re: Integrated: 8274471: Verification of OCSP Response signed with RSASSA-PSS fails

2021-10-05 Thread Wei-Jun Wang
I think it's worth backporting to older LTS releases. Will ask sustaining on it. Thanks, Weijun > On Oct 5, 2021, at 2:36 PM, can comert wrote: > > > Is there any backporting for a LTS version planned?

Re: RFR: 8274656: Remove default_checksum and safe_checksum_type from krb5.conf [v2]

2021-10-05 Thread Valerie Peng
On Mon, 4 Oct 2021 19:32:30 GMT, Weijun Wang wrote: >> Remove support for the 2 settings. Remove classes around the KRB_PRIV and >> KRB_SAFE message types that were never used in Java. > > Weijun Wang has updated the pull request incrementally with one additional > commit since the last revisio

Re: Integrated: 8274471: Verification of OCSP Response signed with RSASSA-PSS fails

2021-10-05 Thread can comert
I have seen the issue is already fixed and will be available for the JDK 18. Thank you very much for your great work and fast response! Is there any backporting for a LTS version planned? Best Regards, Can 4 Eki 2021 Pzt 17:34 tarihinde Weijun Wang şunu yazdı: > On Thu, 30 Sep 2021 15:44:32 GM

Integrated: 8274656: Remove default_checksum and safe_checksum_type from krb5.conf

2021-10-05 Thread Weijun Wang
On Fri, 1 Oct 2021 17:36:13 GMT, Weijun Wang wrote: > Remove support for the 2 settings. Remove classes around the KRB_PRIV and > KRB_SAFE message types that were never used in Java. This pull request has now been integrated. Changeset: 1e752033 Author:Weijun Wang URL: https://git.

Re: RFR: 8274656: Remove default_checksum and safe_checksum_type from krb5.conf [v3]

2021-10-05 Thread Weijun Wang
> Remove support for the 2 settings. Remove classes around the KRB_PRIV and > KRB_SAFE message types that were never used in Java. Weijun Wang has updated the pull request incrementally with one additional commit since the last revision: clean up comment - Changes: - all: http

Integrated: 8273670: Remove weak etypes from default krb5 etype list

2021-10-05 Thread Weijun Wang
On Thu, 23 Sep 2021 14:32:01 GMT, Weijun Wang wrote: > This code change removes weak etypes from the default list so it's safer to > enable one of them. See the corresponding CSR at > https://bugs.openjdk.java.net/browse/JDK-8274207 for more explanation. BTW, > please review the CSR as well.

Re: RFR: 8273670: Remove weak etypes from default krb5 etype list [v5]

2021-10-05 Thread Sean Mullan
On Fri, 1 Oct 2021 17:09:03 GMT, Weijun Wang wrote: >> This code change removes weak etypes from the default list so it's safer to >> enable one of them. See the corresponding CSR at >> https://bugs.openjdk.java.net/browse/JDK-8274207 for more explanation. BTW, >> please review the CSR as well

Re: Different way to solve 8241047

2021-10-05 Thread Sean Mullan
Hi Philippe, On 10/3/21 11:32 AM, Philippe Marschall wrote: Hello First I hope this is the right mailing list. Second, I realize I'm late to the party and this ship may already have sailed. Yes, this is the right mailing list. We're using a third party library from a vendor that calls SSLSe

Please have a quick look at 8274730: AArch64: AES/GCM acceleration is broken by the fix for JDK-8273297

2021-10-05 Thread Andrew Haley
I had to touch common code in C2 to unbreak AArch64, so I'd like another reviewer, please. It's pretty simple, thanks. https://github.com/openjdk/jdk/pull/5819 -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB

Integrated: 8274079: Cleanup unnecessary calls to Throwable.initCause() in java.base module

2021-10-05 Thread Andrey Turbanov
On Thu, 16 Sep 2021 19:03:26 GMT, Andrey Turbanov wrote: > Pass "cause" exception as constructor parameter is shorter and easier to read. This pull request has now been integrated. Changeset: 1459180f Author:Andrey Turbanov Committer: Weijun Wang URL: https://git.openjdk.java.net/

RFR: 8244202: Implementation of JEP 418: Internet-Address Resolution SPI

2021-10-05 Thread Aleksei Efimov
This change implements a new service provider interface for host name and address resolution, so that java.net.InetAddress API can make use of resolvers other than the platform's built-in resolver. The following API classes are added to `java.net.spi` package to facilitate this: - `InetAddressR