On Fri, 2 Jun 2023 12:58:36 GMT, Andrew John Hughes wrote:
>> Currently, security properties are held within the `java.security` file in
>> the JDK tree for each installed JDK. The system property
>> `java.security.properties` can be used to point to a file containing
>> additional properties.
I don’t see the big advantage of changing the dir security property to avoid changing other security property. It would be good if I don’t have to modify the system.properties file, for example by always adding a etc/security.custom.properties file if present, instead. Th
On Fri, 7 Jul 2023 19:21:29 GMT, Pavel Rappo wrote:
> > Took another pass at this, looks good, but I would like to take another
> > last look and make sure that changing the hash code for some of the classes
> > like X509CRL is a benign change.
>
> Thanks, Sean. Take your time, you're an exper
When loading the default JVM trust store, if the JVM trust store contains an
invalid certificate, the exception contains insufficient information to
determine which certificate is invalid, making it very difficult to fix the
problem.
To reproduce the issue:
1. Modify the default JVM trust store
The fix is to remove the expiring SECOM root certificate after approval from
root CA to remove it.
Release note is at - https://bugs.openjdk.org/browse/JDK-8311884
-
Commit messages:
- 8295894: Remove SECOM certificate that is expiring in September 2023
Changes: https://git.openjd
On Tue, 11 Jul 2023 20:42:14 GMT, Rajan Halade wrote:
> The fix is to remove the expiring SECOM root certificate after approval from
> root CA to remove it.
>
> Release note is at - https://bugs.openjdk.org/browse/JDK-8311884
Marked as reviewed by xuelei (Reviewer).
-
PR Review:
On Fri, 7 Jul 2023 23:19:27 GMT, Pavel Rappo wrote:
>> Please review this PR to use modern APIs and language features to simplify
>> `equals` and `hashCode` in security area.
>>
>> I understand that security area is sensitive and a non-expert, such as
>> myself, should tread carefully; so belo
On Tue, 11 Jul 2023 20:42:14 GMT, Rajan Halade wrote:
> The fix is to remove the expiring SECOM root certificate after approval from
> root CA to remove it.
>
> Release note is at - https://bugs.openjdk.org/browse/JDK-8311884
Marked as reviewed by mullan (Reviewer).
-
PR Review:
This change refactors the RSAPadding class to return an output record
containing the status instead of relying on exception object to indicate a
failure.
Thanks in advance for review~
Valerie
-
Commit messages:
- 8302017: Allocate BadPaddingException only if it will be thrown
Cha
On Tue, 11 Jul 2023 20:42:14 GMT, Rajan Halade wrote:
> The fix is to remove the expiring SECOM root certificate after approval from
> root CA to remove it.
>
> Release note is at - https://bugs.openjdk.org/browse/JDK-8311884
This pull request has now been integrated.
Changeset: fd7fddb6
Auth
10 matches
Mail list logo