Integrated: 8309841: Jarsigner should print a warning if an entry is removed

2024-10-02 Thread Weijun Wang
On Fri, 7 Jun 2024 15:11:29 GMT, Weijun Wang wrote: > There ~are two~ is one change~s~: > > 1. In `jarsigner -verify`, check a .SF file contains un-existing entries and > print them out as > > Warning: nonexistent signed entries detected: [a] > > ~2. In `JarSigner::sign0`, when creating a new

Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status [v2]

2024-10-02 Thread Jamil Nimeh
> This PR corrects a flaw in the StatusResponseManager where it was incorrectly > swallowing the interrupt status when either an invokeAll was called (spawning > the threads to fetch each OCSP response) or when attempting to grab the data > from one of the Futures returned from the fetches. > Ad

Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status

2024-10-02 Thread Jamil Nimeh
On Wed, 2 Oct 2024 21:44:08 GMT, Valerie Peng wrote: >> This PR corrects a flaw in the StatusResponseManager where it was >> incorrectly swallowing the interrupt status when either an invokeAll was >> called (spawning the threads to fetch each OCSP response) or when attempting >> to grab the d

Re: RFR: 8309841: Jarsigner should print a warning if an entry is removed [v9]

2024-10-02 Thread Weijun Wang
> There ~are two~ is one change~s~: > > 1. In `jarsigner -verify`, check a .SF file contains un-existing entries and > print them out as > > Warning: nonexistent signed entries detected: [a] > > ~2. In `JarSigner::sign0`, when creating a new .SF file, only include signed > file entries.~ > >

Re: RFR: 8331008: Implement JEP 478: Key Derivation Function API (Preview) [v51]

2024-10-02 Thread Kevin Driver
> Introduce an API for Key Derivation Functions (KDFs), which are cryptographic > algorithms for deriving additional keys from a secret key and other data. See > [JEP 478](https://openjdk.org/jeps/478). > > Work was begun in [another PR](https://github.com/openjdk/jdk/pull/18924). Kevin Driver

Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status

2024-10-02 Thread Valerie Peng
On Fri, 27 Sep 2024 18:48:23 GMT, Jamil Nimeh wrote: > This PR corrects a flaw in the StatusResponseManager where it was incorrectly > swallowing the interrupt status when either an invokeAll was called (spawning > the threads to fetch each OCSP response) or when attempting to grab the data >

Re: RFR: 8339403: sun.security.ssl.StatusResponseManager.get swallows interrupt status

2024-10-02 Thread Valerie Peng
On Fri, 27 Sep 2024 18:48:23 GMT, Jamil Nimeh wrote: > This PR corrects a flaw in the StatusResponseManager where it was incorrectly > swallowing the interrupt status when either an invokeAll was called (spawning > the threads to fetch each OCSP response) or when attempting to grab the data >

Re: RFR: 8331008: Implement JEP 478: Key Derivation Function API (Preview) [v47]

2024-10-02 Thread Kevin Driver
On Tue, 24 Sep 2024 23:31:49 GMT, Weijun Wang wrote: >> Addressed in: >> https://github.com/openjdk/jdk/pull/20301/commits/52ef5b0095dda55491286ede5ad18e38d700124d. > > Have you thought about the test? @wangweij: Thanks for contributing the test in https://github.com/openjdk/jdk/pull/20301/com

Re: RFR: 8331008: Implement JEP 478: Key Derivation Function API (Preview) [v50]

2024-10-02 Thread Kevin Driver
> Introduce an API for Key Derivation Functions (KDFs), which are cryptographic > algorithms for deriving additional keys from a secret key and other data. See > [JEP 478](https://openjdk.org/jeps/478). > > Work was begun in [another PR](https://github.com/openjdk/jdk/pull/18924). Kevin Driver

Re: RFR: 8337496: Improve jarsigner utility handling of missing content [v8]

2024-10-02 Thread Weijun Wang
> There ~are two~ is one change~s~: > > 1. In `jarsigner -verify`, check a .SF file contains un-existing entries and > print them out as > > Warning: nonexistent signed entries detected: [a] > > ~2. In `JarSigner::sign0`, when creating a new .SF file, only include signed > file entries.~ > >

Re: JEP 486: Question about CodeSource

2024-10-02 Thread Sean Mullan
Yes, the code below should continue to work after JEP 486 has been integrated. --Sean On 10/1/24 12:31 PM, Thiago Henrique Hupner wrote: Hi all! Will the following snippet stop working after the JEP 486 has been integrated? If so, will there be any replacement to get a CodeSource? ``` getC