[FELIX-5275] Felix & Equinox handling of OSGI-INF/permissions.perm differs

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Bug
• Affects Version/s: configadmin-1.8.8
• Component/s: Configuration Admin, Framework Security
• Environment: Felix config-admin 1.8.8 running on Equinox with SecurityManager
• External issue URL: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494224
• Assignee: Unassigned
• Reporter: Derek Baum
• Created: 03/Jun/16 16:52
• Updated: 29/Dec/16 10:52
• Resolved: 08/Jul/16 08:49

Description

Using Felix config-admin 1.8.8 in Equinox, with a SecurityManager active, causes the ManagedService.updated() method to get AccessControlExceptions when, for example, accessing System properties.

This is caused by:

#1 OSGI-INF/permissions.perm added to config-admin in FELIX-4039

#2 Different handling of OSGI-INF/permissions.perm between Felix and Equinox.

I have previously raised this problem against Equinox (see External Issue URL), and this is the gist of their analysis:

---------------------------
The felix CM implementation is scoping their own permissions down to a strict subset of permissions and Equinox is correctly enforcing that subset of permissions.

So your bundle tries to read a system property, but the CM impl is not authorized to read that property.

One complication may be that Felix is allowing its bundle protection domains to be configured with the java policy file (because their ProtectionDomains are constructed with that 4 arg constructor).

This would seem to break the specified behavior though, because clearly the CM implementation should never be allowed to have permission to do things outside of what is specified by the permissions.perm file or that are "implied" permissions auto-granted by the framework for each bundle.
-----------------------