RE: ca-certificates-java changes

2017-10-12 Thread Ingo Bauersachs
> Le 30/09/2017 à 17:09, Thorsten Glaser a écrit : > >> IMHO consistency within Debian is *much* more important. >> >> I would be seriously fucked off if I could connect to a host >> using something like wget but not a Java™ application, after >> installing the custom CA into /etc/ssl/certs or si

Re: ca-certificates-java changes

2017-10-12 Thread Thorsten Glaser
Hi Emmanuel, > Similarly I would be seriously fucked off if the application I developed > on another OS would behave differently once deployed on my Debian server > with the same version of Java ;) > > Both use cases are valid I think, maybe we could have it both ways with with an upstream hat o

Re: ca-certificates-java changes

2017-10-12 Thread Emmanuel Bourg
Le 12/10/2017 à 11:58, Emmanuel Bourg a écrit : > 2. ca-certificates-java still generates a keystore from the Debian > certificates but with a different name (cacerts-debian for example). > 3. Patch openjdk to use cacerts-debian in priority if it exists, and > default to cacerts otherwise. Anothe

Re: ca-certificates-java changes

2017-10-12 Thread Emmanuel Bourg
Le 30/09/2017 à 17:09, Thorsten Glaser a écrit : > IMHO consistency within Debian is *much* more important. > > I would be seriously fucked off if I could connect to a host > using something like wget but not a Java™ application, after > installing the custom CA into /etc/ssl/certs or similar, or