Community
Participate
Working Groups
It will be better if we have a preference page (or even add it to the existing ProvisioningPreferencePage) for the unsigned policy constant (eclipse.p2.unsignedPolicy)
I guess this option was present in 3.3 and was explicitly removed in 3.4-3.5. In 3.6 you could use the startup option -Declipse.p2.unsignedPolicy=allow. See discussion at https://bugs.eclipse.org/bugs/show_bug.cgi?id=235526.
We have no immediate plan to work on this. A patch would highly increase the likelihood of fixing this. To get started with the p2 code, see http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Developers The code should likely be part of org.eclipse.equinox.p2.ui and the signature verifier is in the engine bundle.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This is addressed via this commit: https://git.eclipse.org/c/equinox/rt.equinox.p2.git/commit/?id=77ac8abe6f5ec460786e7b68c93b2ff30d34f1d4 *** This bug has been marked as a duplicate of bug 578024 ***