After updating to openjdk version "1.8.0_372"
OpenJDK Runtime Environment (build 1.8.0_372-bre_2023_04_25_03_25-b00)
OpenJDK 64-Bit Server VM (build 25.372-b00, mixed mode)

the tests now pass, so it does seem this is an issue with the JDK that
made the keystore being newish. Only an issue for tests, so I'll
upgrade my vote to +0 on this release. It would be nice to use a more
broadly compatible format for the keystore. Given that the password is
in clear text in the source code on Github, I'm truly not concerned
about a theoretically inferior crypto algorithm being used for this
file, but it's not a release blocker.

On Wed, Apr 26, 2023 at 11:17 PM Elliotte Rusty Harold
<elh...@ibiblio.org> wrote:
>
> On Wed, Apr 26, 2023 at 11:06 PM Jeremy Landis <jeremylan...@hotmail.com> 
> wrote:
> >
> > Without knowing more details myself, couple of possibilities come to mind...
> >
> > - Was keystore made with newer jdk?  See  
> > https://support.oracle.com/knowledge/More%20Applications%20and%20Technologies/2847060_1.html.
> > - Was the keystore filtered?
> >
> > Gut tells me it’s the first issue given how old 1.8.0_172 is (2018-04-17).
> >
>
> Sounds possible. On the same MacBook I see
>
> $ keytool -list -keystore
> maven-resolver-transport-http/src/test/resources/ssl/server-store-selfsigned
> Enter keystore password:
> keytool error: java.io.IOException: Invalid keystore format
>
> --
> Elliotte Rusty Harold
> elh...@ibiblio.org



-- 
Elliotte Rusty Harold
elh...@ibiblio.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to