Bug 239563 - [registry] Secure extension registry using permissions and trust
Summary: [registry] Secure extension registry using permissions and trust
Status: NEW
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Components (show other bugs)
Version: 3.4   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: equinox.compendium-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-04 03:41 EDT by Gunnar Wagenknecht CLA
Modified: 2019-09-06 16:09 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2008-07-04 03:41:45 EDT
Currently, everybody can contribute to every extension point. However, it should be possible to limit this ability in the extension registry using permissions.

The basic use cases would be: declare an extension point as protected and allow only trusted bundles to contribute extensions to it.

A first step could be as simple as x-friends/x-internal. A second step would be to evaluate the bundle signer certificate chain. Both would not require to run the framework with a security manager and can be evaluated at bundle installation time.

A third step could use framework conditional permissions but this requires the security manager.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:09:44 EDT
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.