eclipse - Signed content support in Equinox 3.10 -


in equinox 3.9 (eclipse 4.3) possible configure following properties in eclipse.ini enable authorization.

osgi.signedcontent.support=all osgi.signedcontent.authorization.engine.policy=trusted osgi.framework.keystore=file:truststore.jks 

setting same properties in equinox 3.10 (eclipse 4.4) seems have no effect. can start application regardless wether bundles signed right key or not.

reading documentation there has been no changes.

when code loaded runtime since 3.4, equinox runtime has had ability check signature of code loaded. benefit feature beyond checking signatures during provisioning ability dynamically remove trust , disable code should exploit exposed in deployed code. in order enable signature-based authorization @ load time, following vm argument must passed: -dosgi.signedcontent.support=authority see runtime options page more information osgi.signedcontent.support runtime variable.

any hint or on appreciated. thanks!

the signed content support provisional , got removed part of luna release (see clarification of thomas watson @ equinox mailing list).

opened ticket on suggested thomas (see eclipse bugzilla).


Comments

Popular posts from this blog

android - Gradle sync Error:Configuration with name 'default' not found -

java - Andrioid studio start fail: Fatal error initializing 'null' -

html - jQuery UI Sortable - Remove placeholder after item is dropped -