[13] RFR 8228341: SignTwice.java fails intermittently on Windows

Please review the patch below. This test signs the same jar multiple times. It's mainly about making sure the manifest and signature file can be updated correctly. There is no need to try different key algorithms. We can also use a faster digest algorithm. Thanks, Max diff --git a/test/jdk/Pro

Re: [13] RFR 8227595: keytool/fakegen/DefaultSignatureAlgorithm.java fails due to "exitValue = 6"

Ping again. > On Jul 17, 2019, at 8:32 AM, Weijun Wang wrote: > > JBS: https://bugs.openjdk.java.net/browse/JDK-8227595 > > The test cannot use the included fake keypair generator because on Solaris > the SunPKCS11-Solaris is more preferred. Like what I have done [1] for the > PSS.java test n

Re: RFR[14] Re-enable Stateless Resumption On by default for merge to mainline

I agree we should be consistent. With this change setting the property to "foo" would be false in JDK 13 and true in JDK 14. Typically I think boolean properties are true only if set to "true" (ignoring case), and anything else is false. In hindsight I probably would have also treated the empt

Re: Is Digicert's continued use of the "Distrusted" certificates for code signing still valid?

Hi Sean. Thanks for looking into this issue. I was wondering if there had been any further updates? Regards Bert On Tue, 25 Jun 2019 at 19:08, Bert Eisen wrote: > Hello, > > I’m trying to understand why Digicert are still issuing signing > certificates from the distrusted Symantec root CAs and