On Tue, 4 Mar 2025 13:07:37 GMT, Fernando Guallini
wrote:
> The following tests are marked with @ignore (not running):
>
> - sun/security/ssl/SSLSocketImpl/SetClientMode.java: it checks that setting
> the clientMode after the handshake has begun is not permitted, but this wa
On Fri, 21 Mar 2025 12:00:57 GMT, Fernando Guallini
wrote:
>> The following tests are marked with @ignore (not running):
>>
>> - sun/security/ssl/SSLSocketImpl/SetClientMode.java: it checks that setting
>> the clientMode after the handshake has begun is not permitted,
On Thu, 20 Mar 2025 18:02:49 GMT, Artur Barashev wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> latch await
>
> test/jdk/sun/security/ssl/SSLSocketImpl/SetClien
On Tue, 18 Mar 2025 14:11:26 GMT, Mikhail Yankelevich
wrote:
>> 8351566: Consolidate third party artifacts used in tests
>
> Mikhail Yankelevich has updated the pull request incrementally with one
> additional commit since the last revision:
>
> minor: imports fix
test/lib/jdk/test/lib/secu
l/NonAutoClose.java: This test should only run
> in TLS <= 1.2, as TLSv1.3 changes the behaviour of close_notify. Included
> additional refactoring to ensure test stability.
>
> Executed both tests 10K times, no test flakiness found
Fernando Guallini has updated the pull request in
On Mon, 17 Mar 2025 18:19:46 GMT, Matthew Donovan wrote:
>> The test `javax/net/ssl/DTLS/PacketLossRetransmission` takes about ~2 to
>> complete. The reason is that, in multiple scenarios, the server/client
>> socket times out after 10 seconds waiting to receive a DatagramPacket that
>> has
The test `javax/net/ssl/DTLS/PacketLossRetransmission` takes about ~2 to
complete. The reason is that, in multiple scenarios, the server/client socket
times out after 10 seconds waiting to receive a DatagramPacket that has been
removed (to simulate a packet loss).
After reducing the time out
l/NonAutoClose.java: This test should only run
> in TLS <= 1.2, as TLSv1.3 changes the behaviour of close_notify. Included
> additional refactoring to ensure test stability.
>
> Executed both tests 10K times, no test flakiness found
Fernando Guallini has updated the pull request in
On Tue, 18 Mar 2025 02:27:31 GMT, Artur Barashev wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> SSLContextTemplate and using asserts
>
> test/jdk/sun/security/ssl/SSLSocket
On Tue, 11 Mar 2025 16:48:03 GMT, Matthew Donovan wrote:
>> test/jdk/sun/security/pkcs12/KeytoolOpensslInteropTest.java line 90:
>>
>>> 88: generateInitialKeystores(opensslPath);
>>> 89: testWithJavaCommands();
>>> 90: testWithOpensslCommands(opens
On Tue, 11 Mar 2025 15:21:09 GMT, Matthew Donovan wrote:
> In this PR, I created a new method, `ArtifactResolver.fetchOne()`, to
> consolidate duplicate code across tests.
test/jdk/sun/security/pkcs12/KeytoolOpensslInteropTest.java line 90:
> 88: generateInitialKeystores(openss
On Thu, 13 Feb 2025 12:44:21 GMT, Fernando Guallini
wrote:
> This updates the OpenSSL version that is used by test
> `sun/security/pkcs12/KeytoolOpensslInteropTest.java` to the current LTS
> version (3.0 series).
> There are some differences between the 1.1.x and the current Ope
herefore adding the `-legacy` flag
> when needed to enable it. Additionally, It is also required to specify the
> path location of the legacy provider.
> - Unlike the old version that throws an error if the MAC was absent from the
> PKCS12, the 3.0 series shows a warning instead.
Fe
l/NonAutoClose.java: This test should only run
> in TLS <= 1.2, as TLSv1.3 changes the behaviour of close_notify. Included
> additional refactoring to ensure test stability.
>
> Executed both tests 10K times, no test flakiness found
Fernando Guallini has updated the pull request in
On Thu, 6 Mar 2025 12:54:03 GMT, Matthew Donovan wrote:
>> Well, the test is also checking with java commands if openssl is available
>> (line 75), then it makes sense to keep it when it is not available as it
>> does not rely on Openssl.
>
> My concern is that a Pass result is ambiguous: we ma
On Wed, 5 Mar 2025 13:48:37 GMT, Matthew Donovan wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> SSLContextTemplate and using asserts
>
> test/jdk/sun/security/ssl/SSLSocket
On Wed, 5 Mar 2025 19:45:14 GMT, Matthew Donovan wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> updated wording of openssl version
>
> test/jdk/sun/security/pkcs12/KeytoolO
The following tests are marked with @ignore (not running):
- sun/security/ssl/SSLSocketImpl/SetClientMode.java: it checks that setting the
clientMode after the handshake has begun is not permitted, but this was failing
intermittently due to a race condition, it was possible that SetClientMode wa
On Fri, 21 Feb 2025 10:31:34 GMT, Fernando Guallini
wrote:
> The test javax/crypto/CryptoPermissions/InconsistentEntries.java uses
> CDSTestUtils.clone to copy the JDK into the scratch dir by creating symbolic
> links, but this was seen to crash the VM in Windows Server 2025.
> The test javax/crypto/CryptoPermissions/InconsistentEntries.java uses
> CDSTestUtils.clone to copy the JDK into the scratch dir by creating symbolic
> links, but this was seen to crash the VM in Windows Server 2025. To ensure
> test stability, it should hard copy the required file
The test javax/crypto/CryptoPermissions/InconsistentEntries.java uses
CDSTestUtils.clone to copy the JDK into the scratch dir by creating symbolic
links, but this was seen to crash the VM in Windows Server 2025. To ensure test
stability, it should hard copy the required files.
-
Co
On Mon, 20 Jan 2025 16:20:27 GMT, Fernando Guallini
wrote:
> The test javax/crypto/CryptoPermissions/InconsistentEntries.java should not
> modify the JDK home directory under test as that could impact the results of
> other tests, or it could fail if the JDK home dir is read-only.
On Mon, 5 Aug 2024 10:46:32 GMT, Fernando Guallini
wrote:
> There are 3 manual GSS-API/Kerberos tests that require a manual setup and
> were added to the problem list years ago:
>
> - com/sun/security/sasl/gsskerb/**AuthOnly**-> Verifies that both client and
> server
On Tue, 18 Feb 2025 17:52:14 GMT, Rajan Halade wrote:
>> Fernando Guallini has updated the pull request with a new target base due to
>> a merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contain
herefore adding the `-legacy` flag
> when needed to enable it. Additionally, It is also required to specify the
> path location of the legacy provider.
> - Unlike the old version that throws an error if the MAC was absent from the
> PKCS12, the 3.0 series shows a warning instead.
Fe
On Mon, 20 Jan 2025 16:20:27 GMT, Fernando Guallini
wrote:
> The test javax/crypto/CryptoPermissions/InconsistentEntries.java should not
> modify the JDK home directory under test as that could impact the results of
> other tests, or it could fail if the JDK home dir is read-only.
On Fri, 14 Feb 2025 17:20:11 GMT, Weijun Wang wrote:
> Or "current version". I regret using this in my previous comment. I meant
> "this one particular version" there.
>
> And yes, it will be clear if you mention the "current version as defined by
> ...".
Thanks, updated now
-
P
herefore adding the `-legacy` flag
> when needed to enable it. Additionally, It is also required to specify the
> path location of the legacy provider.
> - Unlike the old version that throws an error if the MAC was absent from the
> PKCS12, the 3.0 series shows a warning instead.
Fe
herefore adding the `-legacy` flag
> when needed to enable it. Additionally, It is also required to specify the
> path location of the legacy provider.
> - Unlike the old version that throws an error if the MAC was absent from the
> PKCS12, the 3.0 series shows a warning instead.
Fe
On Fri, 14 Feb 2025 14:58:55 GMT, Weijun Wang wrote:
> The "preferred version" sounds like user can choose one. I'd rather just say
> "latest version". At least that is the latest our test has access to. Also, I
> assume you will update to newer versions later and this test is not meant to
> r
This updates the OpenSSL version that is used by test
`sun/security/pkcs12/KeytoolOpensslInteropTest.java` to the current LTS version
(3.0 series).
There are some differences between the 1.1.x and the current OpenSSL version:
- RC4 is not longer enabled by default, therefore adding the `-legacy`
On Wed, 2 Oct 2024 13:24:00 GMT, Fernando Guallini
wrote:
> The test: **sun/security/mscapi/nonUniqueAliases/NonUniqueAliases.java**
> relies on the `certutil.exe` tool to import and delete certificates from a
> keystore. It was annotated with `@ignore` due to the uncer
On Fri, 7 Feb 2025 20:22:52 GMT, Rajan Halade wrote:
>> Fernando Guallini has updated the pull request with a new target base due to
>> a merge or a rebase. The pull request now contains five commits:
>>
>> - Merge branch 'master' into 8337723
>&g
On Tue, 11 Feb 2025 13:05:48 GMT, Fernando Guallini
wrote:
>> There are 3 manual GSS-API/Kerberos tests that require a manual setup and
>> were added to the problem list years ago:
>>
>> - com/sun/security/sasl/gsskerb/**AuthOnly**-> Verifies that both client and
&
principal names, generates krb5.conf and
> keytab files, and setup a JAAS login config file.
>
> I've enhanced SaslBasic to include additional wrap/unwrap checks with and
> without a security layer. As a result, the 3 manual tests and their
> associated files are now redundand
principal names, generates krb5.conf and
> keytab files, and setup a JAAS login config file.
>
> I've enhanced SaslBasic to include additional wrap/unwrap checks with and
> without a security layer. As a result, the 3 manual tests and their
> associated files are now redundand
On Thu, 6 Feb 2025 18:11:30 GMT, Mikhail Yankelevich wrote:
>> * ./util/Pem/encoding.sh is now a java test
>> * also added the validations for the test results, not only an error check
>
> Mikhail Yankelevich has updated the pull request incrementally with one
> additional commit since the last
On Wed, 5 Feb 2025 12:53:09 GMT, Fernando Guallini
wrote:
> When compiling the test class: jdk/test/lib/security/timestamp/TsaServer.java
>
>
> Two warning are shown:
>
>
> test/lib/security/timestamp/TsaServer.java:56: warning: [this-escape]
> possible 'th
On Thu, 6 Feb 2025 12:12:35 GMT, Mikhail Yankelevich wrote:
> * ./util/Pem/encoding.sh is now a java test
> * also added the validations for the test results, not only an error check
test/jdk/sun/security/util/Pem/PemEncoding.java line 47:
> 45: File.separator,
> 46:
the test is executed.
>
> Rather than ignoring the test entirely, this PR updates the logic to throw a
> `SkippedException` if the tool is not found, ensuring the test runs when
> possible, and gracefully skipped otherwise.
Fernando Guallini has updated the pull request incrementally wit
On Wed, 5 Feb 2025 22:45:36 GMT, Hai-May Chao wrote:
> Nit: copyright update
updated to 2025 now 👍
-
PR Comment: https://git.openjdk.org/jdk/pull/21305#issuecomment-2639325902
On Wed, 5 Feb 2025 12:53:09 GMT, Fernando Guallini
wrote:
> When compiling the test class: jdk/test/lib/security/timestamp/TsaServer.java
>
>
> Two warning are shown:
>
>
> test/lib/security/timestamp/TsaServer.java:56: warning: [this-escape]
> possible 'th
On Wed, 2 Oct 2024 13:24:00 GMT, Fernando Guallini
wrote:
> The test: **sun/security/mscapi/nonUniqueAliases/NonUniqueAliases.java**
> relies on the `certutil.exe` tool to import and delete certificates from a
> keystore. It was annotated with `@ignore` due to the uncer
When compiling the test class: jdk/test/lib/security/timestamp/TsaServer.java
Two warning are shown:
test/lib/security/timestamp/TsaServer.java:56: warning: [this-escape] possible
'this' escape before subclass is fully initialized
setHandler(handler);
- setHandler is called in th
principal names, generates krb5.conf and
> keytab files, and setup a JAAS login config file.
>
> I've enhanced SaslBasic to include additional wrap/unwrap checks with and
> without a security layer. As a result, the 3 manual tests and their
> associated files are now redundand
The test javax/crypto/CryptoPermissions/InconsistentEntries.java should not
modify the JDK home directory under test as that could impact the results of
other tests, or it could fail if the JDK home dir is read-only.
This PR updates the test to
- clone the tested JDK into the scratch directory
On Wed, 2 Oct 2024 13:24:00 GMT, Fernando Guallini
wrote:
> The test: **sun/security/mscapi/nonUniqueAliases/NonUniqueAliases.java**
> relies on the `certutil.exe` tool to import and delete certificates from a
> keystore. It was annotated with `@ignore` due to the uncer
On Wed, 4 Dec 2024 13:37:32 GMT, Fernando Guallini
wrote:
> The following tests in CAInterop.java for Google test domain are currently
> failing:
>
> security/infra/java/security/cert/CertPathValidator/certification/CAInterop.java#globalsigneccrootcar4
> security/infra/jav
On Thu, 5 Dec 2024 18:12:56 GMT, Rajan Halade wrote:
> LGTM. Can you target this fix to https://github.com/openjdk/jdk/tree/jdk24
> instead?
Done
-
PR Comment: https://git.openjdk.org/jdk/pull/22542#issuecomment-2522683745
On Wed, 4 Dec 2024 14:44:22 GMT, SendaoYan wrote:
> Hi, this test has been marked as manual test by
> [JDK-8334441](https://bugs.openjdk.org/browse/JDK-8334441). After this PR,
> should we mark this test as automatic test.
Hi,
This test should remain manual, as it still depends on multiple ext
The following tests in CAInterop.java for Google test domain are currently
failing:
security/infra/java/security/cert/CertPathValidator/certification/CAInterop.java#globalsigneccrootcar4
security/infra/java/security/cert/CertPathValidator/certification/CAInterop.java#gtsrootcar1
security/infra/ja
On Wed, 23 Oct 2024 14:46:37 GMT, Fernando Guallini
wrote:
> The test sun/security/pkcs11/Provider/RequiredMechCheck.java extends
> sun/security/pkcs11/PKCS11Test.java, which sets up a PKCS11Provider
> configured with NSS config files located in the source tree directory
> (
On Fri, 18 Oct 2024 08:33:36 GMT, Fernando Guallini
wrote:
> Several tests are identified to use weak/legacy algorithms. As these tests
> purpose is not to exercise weak algorithms, these are updated in this PR to
> use stronger algorithms. If the test uses a weak key, it is update
> Several tests are identified to use weak/legacy algorithms. As these tests
> purpose is not to exercise weak algorithms, these are updated in this PR to
> use stronger algorithms. If the test uses a weak key, it is updated as well.
Fernando Guallini has updated the pull request incr
> Several tests are identified to use weak/legacy algorithms. As these tests
> purpose is not to exercise weak algorithms, these are updated in this PR to
> use stronger algorithms. If the test uses a weak key, it is updated as well.
Fernando Guallini has updated the pull request w
On Tue, 1 Oct 2024 08:51:29 GMT, Fernando Guallini
wrote:
> The test
> **sun/security/tools/jarsigner/PreserveRawManifestEntryAndDigest.java** may
> fail with the following exception:
>
>
> test PreserveRawManifestEntryAndDigest.testNameImmediatelyCo
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
On Wed, 30 Oct 2024 23:27:12 GMT, Anthony Scarpino
wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> add more algos to TestExplicitKeyLength.java
>
> test/jdk/com/su
> Several tests are identified to use weak/legacy algorithms. As these tests
> purpose is not to exercise weak algorithms, these are updated in this PR to
> use stronger algorithms. If the test uses a weak key, it is updated as well.
Fernando Guallini has updated the pull request w
On Wed, 30 Oct 2024 23:35:19 GMT, Anthony Scarpino
wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> add more algos to TestExplicitKeyLength.java
>
> test/jdk/java/security/Sign
On Thu, 17 Oct 2024 13:44:19 GMT, Fernando Guallini
wrote:
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a mod
On Thu, 31 Oct 2024 16:58:36 GMT, Sean Mullan wrote:
> LGTM.
Thanks for the review!
-
PR Comment: https://git.openjdk.org/jdk/pull/21280#issuecomment-2450494653
On Wed, 16 Oct 2024 12:34:32 GMT, Fernando Guallini
wrote:
> Several tests currently use weak key and salt sizes. Since the purpose of
> these tests is not to evaluate weak keys, they can be updated to use stronger
> keys length (2048-bits) and stronger Salt (16 bytes). This PR
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request with a new target base due to a
merge or a rebase. The pull request now contains 13 commits:
- Merge branch 'master&#
> Several tests are identified to use weak/legacy algorithms. As these tests
> purpose is not to exercise weak algorithms, these are updated in this PR to
> use stronger algorithms. If the test uses a weak key, it is updated as well.
Fernando Guallini has updated the pull request incr
On Tue, 1 Oct 2024 08:51:29 GMT, Fernando Guallini
wrote:
> The test
> **sun/security/tools/jarsigner/PreserveRawManifestEntryAndDigest.java** may
> fail with the following exception:
>
>
> test PreserveRawManifestEntryAndDigest.testNameImmediatelyCo
Several tests are identified to use weak/legacy algorithms. As these tests
purpose is not to exercise weak algorithms, these are updated in this PR to use
stronger algorithms. If the test uses a weak key, it is updated as well.
-
Commit messages:
- Merge branch 'master' into 834218
On Wed, 23 Oct 2024 19:37:50 GMT, Matthew Donovan wrote:
>> Several tests are identified to use weak/legacy algorithms. As these tests
>> purpose is not to exercise weak algorithms, these are updated in this PR to
>> use stronger algorithms. If the test uses a weak key, it is updated as well.
>
On Wed, 23 Oct 2024 19:50:19 GMT, Rajan Halade wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Reusing Utils.CopyFiles
>
> test/jdk/sun/security/pkcs11/PKCS11Test.java lin
On Wed, 23 Oct 2024 19:43:33 GMT, Matthew Donovan wrote:
>> Fernando Guallini has updated the pull request with a new target base due to
>> a merge or a rebase. The incremental webrev excludes the unrelated changes
>> brought in by the merge/rebase. The pull request contain
onfig files to the Jtreg
> scratch directory and configures the provider to use those files instead.
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
Reusing Utils.CopyFiles
-
Changes:
- all: https://git.openjdk.org/j
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
simplified getTestKeySize
-
Ch
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
On Wed, 23 Oct 2024 19:51:24 GMT, Rajan Halade wrote:
>> The test sun/security/pkcs11/Provider/RequiredMechCheck.java extends
>> sun/security/pkcs11/PKCS11Test.java, which sets up a PKCS11Provider
>> configured with NSS config files located in the source tree directory
>> (sun/security/pkcs11/
The test sun/security/pkcs11/Provider/RequiredMechCheck.java extends
sun/security/pkcs11/PKCS11Test.java, which sets up a PKCS11Provider configured
with NSS config files located in the source tree directory
(sun/security/pkcs11/nss) for the dependent tests to run properly. This test
currently f
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request with a new target base due to a
merge or a rebase. The incremental webrev excludes the unrelated changes
brought in by the m
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
KeyToolTest.java will be updated in another PR
-
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
On Mon, 21 Oct 2024 13:08:09 GMT, Weijun Wang wrote:
>> Fernando Guallini has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Convert bits to bytes when necessary
>
> Have you timed the differences? I remember
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
Updated tests that were already using 2048 to use
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
Fix algo mistake in SignatureKeyInfo
-
Ch
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
Convert bits to bytes when necessary
-
Ch
r algorithms.
>
> There is no significant increase in tests run time, those still complete
> consistently fast (few seconds).
Fernando Guallini has updated the pull request incrementally with one
additional commit since the last revision:
Using SecurityUtils to define the
> Several tests are identified to use weak key parameters (prime modulus,
> private/public values) and certs with weak keys. As these tests purpose is
> not to exercise weak keys, these are updated in this PR to use a modulus with
> 2048-bit, base 2 and certificates with key size 20
Several tests are identified to use weak key parameters (prime modulus,
private/public values) and certs with weak keys. As these tests purpose is not
to exercise weak keys, these are updated in this PR to use a modulus with
2048-bit, base 2 and certificates with key size 2048
-
Co
Several tests currently use weak key and salt sizes. If the purpose of the
tests is not to evaluate weak keys, they should be updated to use stronger
keys. This PR does not intend to update the tests to use stronger algorithms.
There is no significant increase in tests run time, those still run
On Tue, 3 Sep 2024 07:57:47 GMT, Fernando Guallini
wrote:
>> There are 3 manual GSS-API/Kerberos tests that require a manual setup and
>> were added to the problem list years ago:
>>
>> - com/sun/security/sasl/gsskerb/**AuthOnly**-> Verifies that both client and
&
The test: **sun/security/mscapi/nonUniqueAliases/NonUniqueAliases.java** relies
on the `certutil.exe` tool to import and delete certificates from a keystore.
It was annotated with `@ignore` due to the uncertainty of `certutil.exe` being
available on the instance where the test is executed.
Rath
The test
**sun/security/tools/jarsigner/PreserveRawManifestEntryAndDigest.java** may
fail with the following exception:
test PreserveRawManifestEntryAndDigest.testNameImmediatelyContinued(): failure
java.lang.AssertionError: "s k 300 Tue Jun 25 10:20:16 GMT+07:00 2024
META-INF/MANIFEST.MF" sho
his PR updates the maxOutputSize for the DTLS test directory, including
> DTLSRehandshakeTest.java. Incrementing the maxOutputSize results in more
> logs, with an approximate size increase of ~0.6MB when compressed.
Fernando Guallini has updated the pull request incrementally with one
addition
On Tue, 3 Sep 2024 13:07:47 GMT, Fernando Guallini
wrote:
> The test javax/net/ssl/DTLS/DTLSRehandshakeTest.java runs multiple scenarios,
> generating a large amount of logging as a result. Since Jtreg truncates the
> output when it becomes too large, the logs are often not u
On Wed, 11 Sep 2024 09:07:15 GMT, Fernando Guallini
wrote:
> During the code review of
> [JDK-8337664](https://bugs.openjdk.org/browse/JDK-8337664), several
> non-critical comments were raised but not addressed due to time constraints.
> This PR includes the following cha
On Tue, 24 Sep 2024 15:57:28 GMT, Sean Mullan wrote:
>> During the code review of
>> [JDK-8337664](https://bugs.openjdk.org/browse/JDK-8337664), several
>> non-critical comments were raised but not addressed due to time constraints.
>> This PR includes the following changes:
>>
>> 1. Symantec
During the code review of
[JDK-8337664](https://bugs.openjdk.org/browse/JDK-8337664), several
non-critical comments were raised but not addressed due to time constraints.
This PR includes the following changes:
1. Symantec and Entrust tests now reuse common code. The Distrust.java class
contai
On Thu, 15 Aug 2024 09:29:00 GMT, Fernando Guallini
wrote:
> In order to improve performance when instantiating NativePRNG, a dummy
> constructor was added in the PR: https://github.com/openjdk/jdk/pull/17560
> which takes and ignores a `java.security.SecureRandomParameters`, th
On Thu, 5 Sep 2024 09:59:51 GMT, Jaikiran Pai wrote:
> Hello Fernando, I'm not familiar with this test or the area, but if this
> change is just to make available jtreg logs (in a separate file) to allow for
> debugging a currently intermittent test failure, then there are ways to
> change the
R updates the DTLS maxOutputSize for the test directory, including
> DTLSRehandshakeTest.java. Incrementing the maxOutputSize results in more
> logs, with an approximate size increase of 0.6MB when compressed.
Fernando Guallini has updated the pull request with a new target base due to a
On Tue, 27 Aug 2024 14:49:40 GMT, Fernando Guallini
wrote:
> The test sun/security/validator/samedn.sh failed once due to the following
> reason:
>
> `Caused by: java.security.cert.CertificateNotYetValidException: NotBefore:
> Tue Aug 06 14:41:13 GMT 2024`
>
> This t
1 - 100 of 141 matches
Mail list logo
