[
https://issues.apache.org/jira/browse/FELIX-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628970#comment-16628970
]
Timothy Ward commented on FELIX-5911:
-------------------------------------
{quote}[~timothyjward]: as far as I understand the set of permissions granted
by the system admin/the person launching the framework can only be a subset of
the permissions requested in the permissions.perm file. More precisely, the
effective set of permissions is the intersection of the ones in
permissions.perm and the ones granted by the admin. It is hence not possible to
configure additional permissions. Did I get this wrong?
{quote}
You can still use PermissionAdmin/ConditionalPermissionAdmin to control the
permissions of a bundle and grant them wider permissions than they would
otherwise have. You are correct, however that the permissions for a bundle
cannot expand beyond those of the Java runtime as a whole.
> [Configurator] Too restrictive permissions.perm file
> ----------------------------------------------------
>
> Key: FELIX-5911
> URL: https://issues.apache.org/jira/browse/FELIX-5911
> Project: Felix
> Issue Type: Bug
> Components: Configurator
> Affects Versions: configurator-1.0.4, configurator-1.0.6
> Reporter: Christoph Nölle
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: configurator-1.0.8
>
>
> Configurator currently requests
> (java.io.FilePermission "-" "read,write,execute,delete")
> in its permissions.perm file (the "-" means all files and subfolders within
> and below the current working dir). However, the bundle tries to access files
> in the bundle storage area as well, whose location we cannot anticipate here.
> It can be configured by means of a framework property, for instance. The
> correct permission would be
> (java.io.FilePermission "<<ALL FILES>>" "read,write,execute,delete")
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
