|3.6M5: P2 rejects untrusted certificates [message #513605]
||Wed, 10 February 2010 16:46
Registered: July 2009
In our headless build under 3.5, we explicitly sign our plugins using JDK signjar target in postAssemble phase. Although our certificate is untrusted, 3.5 runDirector accepts the signed jars without error. Note p2.gathering=true.|
In 3.6M5, headless build fails in the runDirector target with error "One or more certificates rejected." If I let PDE sign our jars (signJars=true) it still fails with messages like this:
[p2.director] Installation failed.
[p2.director] An error occurred while collecting items to be installed
[p2.director] session context was:(profile=fooProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
[p2.director] Problems downloading artifact: osgi.bundle,org.eclipse.cdt.core.win32,184.108.40.206002011403.
[p2.director] Error reading signed content:C:\DOCUME~1\foo\LOCALS~1\Temp\signatureFile63413.jar
If I don't sign jars at all, the build completes without problem.
So, I think p2 in 3.6 now requires trusted certificates. We are not ready to get our certs trusted, but would like to continue signing our jars. Is there a workaround or other p2 option to relax this constraint? Is this a bug?
Powered by FUDForum
. Page generated in 0.05473 seconds