On Tue, 21 May 2024 17:41:46 GMT, Volodymyr Paprotski wrote:
>> Performance. Before:
>>
>> Benchmark(algorithm) (dataSize) (keyLength)
>> (provider) Mode Cnt ScoreError Units
>> SignatureBench.ECDSA.signSHA256withECDSA1024 256
For this PR, I identified TLS tests that can fail due to hard-code certificates
expiring. I updated those tests to use certificates that are generated
programmatically. This includes adding some helper methods to the
CertificateBuilder class to create builder objects with common default values.
On Thu, 25 Apr 2024 17:20:11 GMT, Matthew Donovan wrote:
> For this PR, I identified TLS tests that can fail due to hard-code
> certificates expiring. I updated those tests to use certificates that are
> generated programmatically. This includes adding some helper methods to the
> CertificateB
On Tue, 21 May 2024 17:47:47 GMT, Valerie Peng wrote:
> Changes look good to me. Thanks~
Thanks a lot! Can you please also review the CSR?
-
PR Comment: https://git.openjdk.org/jdk/pull/19216#issuecomment-2123163145
On Mon, 20 May 2024 23:22:17 GMT, Weijun Wang wrote:
>> Add a new system property to control the name comparison in keytab and
>> ccache entry lookup.
>
> Weijun Wang has updated the pull request incrementally with two additional
> commits since the last revision:
>
> - remove commented out c
On Tue, 21 May 2024 07:21:14 GMT, Tobias Hartmann wrote:
>> Volodymyr Paprotski has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> shenandoah verifier
>
> I'm getting some conflicts when trying to apply this to master. Could you
> please m
> Performance. Before:
>
> Benchmark(algorithm) (dataSize) (keyLength)
> (provider) Mode Cnt ScoreError Units
> SignatureBench.ECDSA.signSHA256withECDSA1024 256
> thrpt3 6443.934 ± 6.491 ops/s
> SignatureBench.ECDSA.
On Tue, 21 May 2024 08:44:47 GMT, Maurizio Cimadamore
wrote:
> These are all good suggestions. I have not looked into jpackage, but yes, I
> would expect that the jpackage user would need to provide extra options when
> packaging the application.
It would be good to document how jpackage user
On Fri, 17 May 2024 13:38:25 GMT, Maurizio Cimadamore
wrote:
>> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting
>> the use of JNI in the following ways:
>>
>> * `System::load` and `System::loadLibrary` are now restricted methods
>> * `Runtime::load` and `Runtime::loa
On Fri, 17 May 2024 13:38:25 GMT, Maurizio Cimadamore
wrote:
>> This PR implements [JEP 472](https://openjdk.org/jeps/472), by restricting
>> the use of JNI in the following ways:
>>
>> * `System::load` and `System::loadLibrary` are now restricted methods
>> * `Runtime::load` and `Runtime::loa
On Tue, 21 May 2024 07:20:05 GMT, Alan Bateman wrote:
> > Have you looked into / thought about how this will work for jpackaged apps
> > ? I suspect that both the existing FFM usage and this will be options the
> > application packager will need to supply when building the jpackaged app -
> >
On Fri, 17 May 2024 21:16:47 GMT, Volodymyr Paprotski wrote:
>> Performance. Before:
>>
>> Benchmark(algorithm) (dataSize) (keyLength)
>> (provider) Mode Cnt ScoreError Units
>> SignatureBench.ECDSA.signSHA256withECDSA1024 256
On Mon, 20 May 2024 18:47:35 GMT, Phil Race wrote:
> Have you looked into / thought about how this will work for jpackaged apps ?
> I suspect that both the existing FFM usage and this will be options the
> application packager will need to supply when building the jpackaged app -
> the end use
On Fri, 17 May 2024 21:16:47 GMT, Volodymyr Paprotski wrote:
>> Performance. Before:
>>
>> Benchmark(algorithm) (dataSize) (keyLength)
>> (provider) Mode Cnt ScoreError Units
>> SignatureBench.ECDSA.signSHA256withECDSA1024 256
14 matches
Mail list logo
