Equinox 3.10 中的签名内容支持
Signed content support in Equinox 3.10
在 Equinox 3.9 (Eclipse 4.3) 中，可以在 eclipse.ini 中配置以下属性以启用授权。
osgi.signedcontent.support=all
osgi.signedcontent.authorization.engine.policy=trusted
osgi.framework.keystore=file:truststore.jks
在 Equinox 3.10 (Eclipse 4.4) 中设置相同的属性似乎没有效果。无论我的包是否使用正确的密钥签名，我都可以启动应用程序。
正在阅读 documentation 我会说没有任何变化。
When code is loaded by the runtime
Since 3.4, the Equinox runtime has had the ability to check the signature of code as it is loaded. The benefit to this feature beyond checking signatures during provisioning is the ability to dynamically remove trust and disable code should an exploit be exposed in deployed code. In order to enable signature-based authorization at load time, the following VM argument must be passed:
-Dosgi.signedcontent.support=authority
See the runtime options page for more information about the osgi.signedcontent.support runtime variable.
非常感谢任何提示或帮助。谢谢！
签名内容支持只是临时的，已作为 Luna 版本的一部分被删除（请参阅 equinox mailing list 上 Thomas Watson 的说明）。
按照 Thomas 的建议开了一张票（参见 Eclipse Bugzilla）。
在 Equinox 3.9 (Eclipse 4.3) 中，可以在 eclipse.ini 中配置以下属性以启用授权。
osgi.signedcontent.support=all
osgi.signedcontent.authorization.engine.policy=trusted
osgi.framework.keystore=file:truststore.jks
在 Equinox 3.10 (Eclipse 4.4) 中设置相同的属性似乎没有效果。无论我的包是否使用正确的密钥签名，我都可以启动应用程序。
正在阅读 documentation 我会说没有任何变化。
When code is loaded by the runtime Since 3.4, the Equinox runtime has had the ability to check the signature of code as it is loaded. The benefit to this feature beyond checking signatures during provisioning is the ability to dynamically remove trust and disable code should an exploit be exposed in deployed code. In order to enable signature-based authorization at load time, the following VM argument must be passed: -Dosgi.signedcontent.support=authority See the runtime options page for more information about the osgi.signedcontent.support runtime variable.
非常感谢任何提示或帮助。谢谢！
签名内容支持只是临时的，已作为 Luna 版本的一部分被删除（请参阅 equinox mailing list 上 Thomas Watson 的说明）。
按照 Thomas 的建议开了一张票（参见 Eclipse Bugzilla）。