Gunnar, David (and others). Thank-you for the pointers. It's actually very easy to fetch the certs, install them in your own truststore and verify them that way. I will write this up for others.
There is still the workflow question, is this the best way for users to consume content from a p2 site with a self signed certificate? But at least it is 'a' solution. Cheers, Ian On Mon, Apr 15, 2013 at 11:38 AM, Ian Bull <[email protected]> wrote: > I've not tried that. I think this is the same suggestion David W. made on > [1]. The idea [2] (if I understand it correctly) is to import the root cert > for the self-signed certificate into a custom trust store, and then use > that when starting Eclipse. > > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=318339#c3 > [2] > https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/5/html/Security_Guide/ch15s02s02.html > > I'm gathering the keys now. I'll update everyone on my progress. > > Cheers, > Ian > > > On Mon, Apr 15, 2013 at 11:26 AM, Gunnar Wagenknecht < > [email protected]> wrote: > >> Am 12.04.2013 23:31, schrieb Ian Bull: >> >> What do others think? Is this a really bad idea? Are others hitting this >>> problem too or is it just me? >>> >> >> Did you try setting a default custom truststore when starting Eclipse? >> >> .. -Djavax.net.ssl.* >> >> -Gunnar >> >> -- >> Gunnar Wagenknecht >> [email protected] >> http://wagenknecht.org/ >> >> ______________________________**_________________ >> p2-dev mailing list >> [email protected] >> https://dev.eclipse.org/**mailman/listinfo/p2-dev<https://dev.eclipse.org/mailman/listinfo/p2-dev> >> > > > > -- > R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 > http://eclipsesource.com | http://twitter.com/eclipsesource > -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource
_______________________________________________ p2-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/p2-dev
