Integrated: 8356977: UTF-8 cleanups

2025-06-04 Thread Magnus Ihse Bursie
On Wed, 14 May 2025 14:23:31 GMT, Magnus Ihse Bursie wrote: > I found a few other places in the code that can be cleaned up after the > conversion to UTF-8. This pull request has now been integrated. Changeset: edf92721 Author:Magnus Ihse Bursie URL: https://git.openjdk.org/jdk/com

Integrated: 8350689: Turn on timestamp and thread metadata by default for java.security.debug

2025-06-04 Thread Sean Coffey
On Thu, 29 May 2025 19:06:15 GMT, Sean Coffey wrote: > Removal of the `+thread` and `+timestamp` options that were used to control > the logging behavior of output from the `java.security.debug` system property. > > > To enhance the security debug logs, the thread and timestamp data should >

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v2]

2025-06-04 Thread Varada M
> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" > throws NoSuchAlgorithmException. > This patch restores the behavior by ensuring that empty mode or padding > strings are interpreted as null. > > Testing done for : tier1 - fastdebug level (AIX) > > JBS: [JDK-8358159

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Varada M
> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" > throws NoSuchAlgorithmException. > This patch restores the behavior by ensuring that empty mode or padding > strings are interpreted as null. > > Testing done for : tier1 - fastdebug level (AIX) > > JBS: [JDK-8358159

Re: RFR: 8355379: Annotate lazy fields in java.security @Stable

2025-06-04 Thread Per Minborg
On Fri, 23 May 2025 04:54:26 GMT, Koushik Muthukrishnan Thirupattur wrote: > Several classes in the `java.security` package lazily compute their hash > value and store it in a field. These fields can typically be annotated with > the `@Stable` annotation. Many of the current implementations ar

Re: RFR: 8358171: Additional code coverage for PEM API [v2]

2025-06-04 Thread Fernando Guallini
> The tests included in this PR add code coverage mainly to the following > classes introduced/updated by JEP 470 (PEM): PEMDecoder, PEMEncoder, Pem, > EncryptedPrivateKeyInfo and the Key factories. In addition, more tests are > included for RSAPSS, multithreading, _jdk.epkcs8.defaultAlgorithm_

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Amit Kumar
On Wed, 4 Jun 2025 10:37:28 GMT, Varada M wrote: >> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" >> throws NoSuchAlgorithmException. >> This patch restores the behavior by ensuring that empty mode or padding >> strings are interpreted as null. >> >> Testing done f

RFR: 8358451: SunJCE PBEKey impl should throw IllegalStateException when getEncoded() is called

2025-06-04 Thread Valerie Peng
Update the `PBEKey` class of the SunJCE provider which override the `javax.security.auth.Destroyable` interface to 1. throw `IllegalStateException` if `getEncoded()` is called after key is destroyed 2. serialization of such destroyed `PBEKey` object will lead to exception. Also update the `P

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Sean Mullan
On Wed, 4 Jun 2025 10:37:28 GMT, Varada M wrote: >> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" >> throws NoSuchAlgorithmException. >> This patch restores the behavior by ensuring that empty mode or padding >> strings are interpreted as null. >> >> Testing done f

RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key

2025-06-04 Thread Weijun Wang
Add more comment on why `KeyUtil::getKeySize` could return -1. Add a new method `getNistCategory` to get the NIST security category. - Commit messages: - the fix Changes: https://git.openjdk.org/jdk/pull/25642/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=25642&range=00

Re: RFR: 8358451: SunJCE PBEKey impl should throw IllegalStateException when getEncoded() is called

2025-06-04 Thread Weijun Wang
On Wed, 4 Jun 2025 03:10:29 GMT, Valerie Peng wrote: > Update the `PBEKey` class of the SunJCE provider which override the > `javax.security.auth.Destroyable` interface to > > 1. throw `IllegalStateException` if `getEncoded()` is called after key is > destroyed > 2. serialization of such dest

Re: RFR: 8358451: SunJCE PBEKey impl should throw IllegalStateException when getEncoded() is called

2025-06-04 Thread Weijun Wang
On Wed, 4 Jun 2025 03:10:29 GMT, Valerie Peng wrote: > Update the `PBEKey` class of the SunJCE provider which override the > `javax.security.auth.Destroyable` interface to > > 1. throw `IllegalStateException` if `getEncoded()` is called after key is > destroyed > 2. serialization of such dest

Re: RFR: 8349910: Implement JEP 517: HTTP/3 for the HTTP Client API [v6]

2025-06-04 Thread Daniel Fuchs
> Hi, > > Please find here a PR for the implementation of [JEP 517: HTTP/3 for the HTTP > Client API](https://openjdk.org/jeps/517). > > The CSR can be viewed at [JDK-8350588: Implement JEP 517: HTTP/3 for the HTTP > Client API](https://bugs.openjdk.org/browse/JDK-8350588) > > This JEP propose

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key

2025-06-04 Thread Mark Powers
On Wed, 4 Jun 2025 14:59:43 GMT, Weijun Wang wrote: > Add more comment on why `KeyUtil::getKeySize` could return -1. Add a new > method `getNistCategory` to get the NIST security category. src/java.base/share/classes/sun/security/util/KeyUtil.java line 56: > 54: * Traditionally, the key s

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key

2025-06-04 Thread Artur Barashev
On Wed, 4 Jun 2025 14:59:43 GMT, Weijun Wang wrote: > Add more comment on why `KeyUtil::getKeySize` could return -1. Add a new > method `getNistCategory` to get the NIST security category. src/java.base/share/classes/sun/security/util/KeyUtil.java line 62: > 60: * each standardized parame

Re: RFR: 8349910: Implement JEP 517: HTTP/3 for the HTTP Client API [v5]

2025-06-04 Thread Daniel Fuchs
On Fri, 16 May 2025 10:26:11 GMT, Daniel Fuchs wrote: >> Daniel Fuchs has updated the pull request with a new target base due to a >> merge or a rebase. The pull request now contains 422 commits: >> >> - merge latest changes from master branch >> - Undo whitespace change >> - Remove unnecess

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key [v2]

2025-06-04 Thread Weijun Wang
> Add more comment on why `KeyUtil::getKeySize` could return -1. Add a new > method `getNistCategory` to get the NIST security category. Weijun Wang has updated the pull request incrementally with one additional commit since the last revision: addressing Mark's comments - Change

Re: RFR: 8358171: Additional code coverage for PEM API [v3]

2025-06-04 Thread Fernando Guallini
> The tests included in this PR add code coverage mainly to the following > classes introduced/updated by JEP 470 (PEM): PEMDecoder, PEMEncoder, Pem, > EncryptedPrivateKeyInfo and the Key factories. In addition, more tests are > included for RSAPSS, multithreading, _jdk.epkcs8.defaultAlgorithm_

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key [v2]

2025-06-04 Thread Weijun Wang
On Wed, 4 Jun 2025 16:08:31 GMT, Artur Barashev wrote: >> Weijun Wang has updated the pull request incrementally with one additional >> commit since the last revision: >> >> addressing Mark's comments > > src/java.base/share/classes/sun/security/util/KeyUtil.java line 62: > >> 60: * eac

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Valerie Peng
On Wed, 4 Jun 2025 13:39:50 GMT, Sean Mullan wrote: > @valeriepeng Can you also review this? Thanks. Yes, I have started looking at it. Was about to ask for a regression test, and you beat me to it. - PR Comment: https://git.openjdk.org/jdk/pull/25547#issuecomment-2940866076

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key [v2]

2025-06-04 Thread Artur Barashev
On Wed, 4 Jun 2025 16:50:41 GMT, Weijun Wang wrote: >> src/java.base/share/classes/sun/security/util/KeyUtil.java line 62: >> >>> 60: * each standardized parameter set. For example, ML-KEM-768 is >>> assigned to >>> 61: * category 3, and ML-DSA-87 to category 5. >>> 62: * >> >>

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Valerie Peng
On Wed, 4 Jun 2025 10:37:28 GMT, Varada M wrote: >> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" >> throws NoSuchAlgorithmException. >> This patch restores the behavior by ensuring that empty mode or padding >> strings are interpreted as null. >> >> Testing done f

Re: RFR: 8349910: Implement JEP 517: HTTP/3 for the HTTP Client API [v6]

2025-06-04 Thread Daniel Fuchs
On Wed, 4 Jun 2025 15:46:36 GMT, Daniel Fuchs wrote: >> Hi, >> >> Please find here a PR for the implementation of [JEP 517: HTTP/3 for the >> HTTP Client API](https://openjdk.org/jeps/517). >> >> The CSR can be viewed at [JDK-8350588: Implement JEP 517: HTTP/3 for the >> HTTP Client API](http

Re: RFR: 8357592: Update output parsing in test/jdk/sun/security/tools/jarsigner/compatibility/Compatibility.java

2025-06-04 Thread Rajan Halade
On Thu, 22 May 2025 23:03:47 GMT, Matthew Donovan wrote: > In this PR, I updated the jarsigner compatibility test to handle minor > differences in the output of jarsigner between versions. Marked as reviewed by rhalade (Reviewer). - PR Review: https://git.openjdk.org/jdk/pull/2540

Integrated: 8357592: Update output parsing in test/jdk/sun/security/tools/jarsigner/compatibility/Compatibility.java

2025-06-04 Thread Matthew Donovan
On Thu, 22 May 2025 23:03:47 GMT, Matthew Donovan wrote: > In this PR, I updated the jarsigner compatibility test to handle minor > differences in the output of jarsigner between versions. This pull request has now been integrated. Changeset: 5ed246d1 Author:Matthew Donovan URL: ht

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Valerie Peng
On Wed, 4 Jun 2025 10:37:28 GMT, Varada M wrote: >> Omitting the mode/padding in a transformation string eg: "AES/ /NoPadding" >> throws NoSuchAlgorithmException. >> This patch restores the behavior by ensuring that empty mode or padding >> strings are interpreted as null. >> >> Testing done f

Re: RFR: 8358159: Empty mode/padding in cipher transformations [v3]

2025-06-04 Thread Valerie Peng
On Wed, 4 Jun 2025 18:06:33 GMT, Valerie Peng wrote: >> Varada M has updated the pull request incrementally with one additional >> commit since the last revision: >> >> whitespace error fix > > src/java.base/share/classes/javax/crypto/Cipher.java line 393: > >> 391: this.suffix =

Re: RFR: 8349550: Improve SASL random usage [v4]

2025-06-04 Thread Sean Mullan
On Fri, 30 May 2025 18:19:13 GMT, Koushik Muthukrishnan Thirupattur wrote: >> Check Digest-MD5 utilities SecureRandom Usage and update random usage with >> secure random > > Koushik Muthukrishnan Thirupattur has updated the pull request with a new > target base due to a merge or a rebase. The

Re: RFR: 8358099: PEM spec updates [v2]

2025-06-04 Thread Sean Mullan
On Tue, 3 Jun 2025 16:24:44 GMT, Sean Mullan wrote: >> Anthony Scarpino has updated the pull request incrementally with one >> additional commit since the last revision: >> >> comments > > src/java.base/share/classes/java/security/PEMDecoder.java line 127: > >> 125: * @implNote An implement

Re: RFR: 8358099: PEM spec updates [v3]

2025-06-04 Thread Anthony Scarpino
> Hi, I need a review of some PEM updates. `PEMRecord.pem` is renamed to > `content` to better describe that it is the base64 content and not including > the header and footer. Additionally, `PEMRecord.getEncoded()` is removed and > some javadoc clarifications for PEMEncoder and PEMDecoder. Th

Re: RFR: 8358594: Misleading keyLength value captured in JFR event for ML-KEM key [v3]

2025-06-04 Thread Weijun Wang
> Add more comment on why `KeyUtil::getKeySize` could return -1. Add a new > method `getNistCategory` to get the NIST security category. Weijun Wang has updated the pull request incrementally with one additional commit since the last revision: enhance test to be exhaustive - Cha

Re: RFR: 8358171: Additional code coverage for PEM API [v3]

2025-06-04 Thread Anthony Scarpino
On Wed, 4 Jun 2025 16:49:11 GMT, Fernando Guallini wrote: >> The tests included in this PR add code coverage mainly to the following >> classes introduced/updated by JEP 470 (PEM): PEMDecoder, PEMEncoder, Pem, >> EncryptedPrivateKeyInfo and the Key factories. In addition, more tests are >> in