Re: RFR: 8255266: 2021-11-27 public suffix list update v 3c213aa

2022-02-18 Thread Ahmad shabib
On Thu, 17 Feb 2022 23:28:35 GMT, Weijun Wang wrote: > Updating to a recent release of PSL. Marked as reviewed by ahmadsha...@github.com (no known OpenJDK username). - PR: https://git.openjdk.java.net/jdk/pull/7526

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Alan Bateman
On Thu, 17 Feb 2022 19:00:47 GMT, Lance Andersen wrote: >> Hi all, >> >> Please review the attached patch to address >> >> - That JarFile::getInputStream did not check for a null ZipEntry passed as a >> parameter >> - Have Zip/JarFile::getInputStream throw a ZipException in the event that an

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v5]

2022-02-18 Thread Weijun Wang
On Fri, 18 Feb 2022 06:56:04 GMT, Michael Osipov wrote: >> Yes. I don't want to let the method fail. Since `instanceof String` should >> be called anyway the caller can decide how to fail. > > So you leave it to the user to read the ASN.1 value and fail if the encoding > is incorrect instead of

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v5]

2022-02-18 Thread Michael Osipov
On Fri, 18 Feb 2022 15:06:07 GMT, Weijun Wang wrote: >> So you leave it to the user to read the ASN.1 value and fail if the encoding >> is incorrect instead of throwing a `Ceritificate..Exception` although other >> GeneralNames do? > > I want to minimize behavior change and I'm leaving them to

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Lance Andersen
On Fri, 18 Feb 2022 12:09:53 GMT, Alan Bateman wrote: > The updates changes to ZipFile/JarFile look okay. I don't have time to study > the test too closely right now but it will need to include instructions on > how to re-create the signed JAR that is stored in the byte array. Those instructio

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v5]

2022-02-18 Thread Weijun Wang
On Fri, 18 Feb 2022 15:17:30 GMT, Michael Osipov wrote: >> I want to minimize behavior change and I'm leaving them to notice there's no >> string there and fail. > > While I understand that, `new DerValue(byte[])` will be ignored and this will > be also inconsistent with the remaining general n

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v5]

2022-02-18 Thread Sean Mullan
On Fri, 18 Feb 2022 16:28:25 GMT, Weijun Wang wrote: >> While I understand that, `new DerValue(byte[])` will be ignored and this >> will be also inconsistent with the remaining general names. Looking at >> sun.security.x509.GeneralName.GeneralName(DerValue, boolean) they all throw >> `IOExcept

Integrated: 8255266: Update Public Suffix List to 3c213aa

2022-02-18 Thread Weijun Wang
On Thu, 17 Feb 2022 23:28:35 GMT, Weijun Wang wrote: > Updating to a recent release of PSL. This pull request has now been integrated. Changeset: 7ce75afb Author:Weijun Wang URL: https://git.openjdk.java.net/jdk/commit/7ce75afbbcca7635356c7377be7ddff15335e563 Stats: 1254 lines i

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Alan Bateman
On Fri, 18 Feb 2022 16:25:30 GMT, Lance Andersen wrote: > > The updates changes to ZipFile/JarFile look okay. I don't have time to > > study the test too closely right now but it will need to include > > instructions on how to re-create the signed JAR that is stored in the byte > > array. > >

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Lance Andersen
On Fri, 18 Feb 2022 17:05:53 GMT, Alan Bateman wrote: > > > The updates changes to ZipFile/JarFile look okay. I don't have time to > > > study the test too closely right now but it will need to include > > > instructions on how to re-create the signed JAR that is stored in the > > > byte array

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Alan Bateman
On Fri, 18 Feb 2022 17:15:17 GMT, Lance Andersen wrote: > If you feel there is still something lacking for documentation, I can > certainly make another pass clarify/add it, but I tried to cover the steps > (but I also understand what might be obvious to me might not be as obvious as > I thoug

RFR: 8277488: Add expiry exception for Digicert (geotrustglobalca) expiring in May 2022

2022-02-18 Thread Rajan Halade
We are checking with CA if root cert can be removed. Meanwhile, updated test to add expiry exception. - Commit messages: - 8277488: Add expiry exception for Digicert (geotrustglobalca) expiring in May 2022 Changes: https://git.openjdk.java.net/jdk/pull/7537/files Webrev: https://

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v5]

2022-02-18 Thread Michael StJohns
OtherName.java @93,97 PR:https://git.openjdk.java.net/jdk/pull/7167     if (derValue1.isContextSpecific((byte) 0) && derValue1.isConstructed()) {     nameValue = derValue1.data.toByteArray();     } else {     throw new IOException("value is not [0]");     } That ex

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v5]

2022-02-18 Thread Lance Andersen
> Hi all, > > Please review the attached patch to address > > - That JarFile::getInputStream did not check for a null ZipEntry passed as a > parameter > - Have Zip/JarFile::getInputStream throw a ZipException in the event that an > unexpected exception occurs > > Mach5 tiers1-3 runs are clean

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v4]

2022-02-18 Thread Lance Andersen
On Fri, 18 Feb 2022 17:20:26 GMT, Alan Bateman wrote: > > If you feel there is still something lacking for documentation, I can > > certainly make another pass clarify/add it, but I tried to cover the steps > > (but I also understand what might be obvious to me might not be as obvious > > as I

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v6]

2022-02-18 Thread Lance Andersen
> Hi all, > > Please review the attached patch to address > > - That JarFile::getInputStream did not check for a null ZipEntry passed as a > parameter > - Have Zip/JarFile::getInputStream throw a ZipException in the event that an > unexpected exception occurs > > Mach5 tiers1-3 runs are clean

Re: RFR: 8280409: JarFile::getInputStream can fail with NPE accessing ze.getName() [v7]

2022-02-18 Thread Lance Andersen
> Hi all, > > Please review the attached patch to address > > - That JarFile::getInputStream did not check for a null ZipEntry passed as a > parameter > - Have Zip/JarFile::getInputStream throw a ZipException in the event that an > unexpected exception occurs > > Mach5 tiers1-3 runs are clean

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v8]

2022-02-18 Thread Weijun Wang
On Thu, 17 Feb 2022 16:00:46 GMT, Weijun Wang wrote: >> The enhancement adds two extra items in the `getSubjectAlternativeNames()` >> output for an OtherName. >> >> It also fix several errors: >> 1. In `OtherName.java`, `nameValue` should be the value inside `CONTEXT [0]` >> without the tag an

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v9]

2022-02-18 Thread Weijun Wang
> The enhancement adds two extra items in the `getSubjectAlternativeNames()` > output for an OtherName. > > It also fix several errors: > 1. In `OtherName.java`, `nameValue` should be the value inside `CONTEXT [0]` > without the tag and length bytes. > 2. The argument in constructor `extClass.ge

Re: RFR: 8277488: Add expiry exception for Digicert (geotrustglobalca) expiring in May 2022

2022-02-18 Thread Weijun Wang
On Fri, 18 Feb 2022 18:24:46 GMT, Rajan Halade wrote: > We are checking with CA if root cert can be removed. Meanwhile, updated test > to add expiry exception. Looks fine to me. - Marked as reviewed by weijun (Reviewer). PR: https://git.openjdk.java.net/jdk/pull/7537

Integrated: 8277488: Add expiry exception for Digicert (geotrustglobalca) expiring in May 2022

2022-02-18 Thread Rajan Halade
On Fri, 18 Feb 2022 18:24:46 GMT, Rajan Halade wrote: > We are checking with CA if root cert can be removed. Meanwhile, updated test > to add expiry exception. This pull request has now been integrated. Changeset: d3749de4 Author:Rajan Halade URL: https://git.openjdk.java.net/jdk/c

RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error

2022-02-18 Thread Valerie Peng
Could someone please help review this trivial change? This is to add an error handling for the potential CKR_BUFFER_TOO_SMALL error when calling C_Sign(). Since none of the supported signature algorithms trigger this error as the default buffer size is large enough, this is more for consistency

Re: RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error

2022-02-18 Thread Mikael Vidstedt
On Fri, 18 Feb 2022 21:52:59 GMT, Valerie Peng wrote: > Could someone please help review this trivial change? This is to add an error > handling for the potential CKR_BUFFER_TOO_SMALL error when calling C_Sign(). > Since none of the supported signature algorithms trigger this error as the > de

Re: RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error

2022-02-18 Thread Valerie Peng
On Fri, 18 Feb 2022 22:10:17 GMT, Mikael Vidstedt wrote: >> Could someone please help review this trivial change? This is to add an >> error handling for the potential CKR_BUFFER_TOO_SMALL error when calling >> C_Sign(). Since none of the supported signature algorithms trigger this >> error as

Re: RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error [v2]

2022-02-18 Thread Valerie Peng
> Could someone please help review this trivial change? This is to add an error > handling for the potential CKR_BUFFER_TOO_SMALL error when calling C_Sign(). > Since none of the supported signature algorithms trigger this error as the > default buffer size is large enough, this is more for cons

Re: RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error [v2]

2022-02-18 Thread Mikael Vidstedt
On Sat, 19 Feb 2022 00:07:34 GMT, Valerie Peng wrote: >> Could someone please help review this trivial change? This is to add an >> error handling for the potential CKR_BUFFER_TOO_SMALL error when calling >> C_Sign(). Since none of the supported signature algorithms trigger this >> error as th

Re: RFR: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error [v2]

2022-02-18 Thread Valerie Peng
On Sat, 19 Feb 2022 00:07:34 GMT, Valerie Peng wrote: >> Could someone please help review this trivial change? This is to add an >> error handling for the potential CKR_BUFFER_TOO_SMALL error when calling >> C_Sign(). Since none of the supported signature algorithms trigger this >> error as th

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v8]

2022-02-18 Thread Michael StJohns
On 2/18/2022 3:05 PM, Weijun Wang wrote: On Thu, 17 Feb 2022 16:00:46 GMT, Weijun Wang wrote: The enhancement adds two extra items in the `getSubjectAlternativeNames()` output for an OtherName. It also fix several errors: 1. In `OtherName.java`, `nameValue` should be the value inside `CONTEX

Re: RFR: 8277976: Break up SEQUENCE in X509Certificate::getSubjectAlternativeNames and X509Certificate::getIssuerAlternativeNames in otherName [v9]

2022-02-18 Thread Weijun Wang
On Fri, 18 Feb 2022 20:05:46 GMT, Weijun Wang wrote: >> The enhancement adds two extra items in the `getSubjectAlternativeNames()` >> output for an OtherName. >> >> It also fix several errors: >> 1. In `OtherName.java`, `nameValue` should be the value inside `CONTEXT [0]` >> without the tag an

Integrated: 8282077: PKCS11 provider C_sign() impl should handle CKR_BUFFER_TOO_SMALL error

2022-02-18 Thread Valerie Peng
On Fri, 18 Feb 2022 21:52:59 GMT, Valerie Peng wrote: > Could someone please help review this trivial change? This is to add an error > handling for the potential CKR_BUFFER_TOO_SMALL error when calling C_Sign(). > Since none of the supported signature algorithms trigger this error as the > de