[ 
https://issues.apache.org/jira/browse/FELIX-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704657#action_12704657
 ] 

Karl Pauls edited comment on FELIX-1103 at 4/30/09 7:59 AM:
------------------------------------------------------------

Ah ok, you are talking about the normal FilePermission. Well, we don't do 
anything special with it so I was assuming it would be already doing what it 
should. I will investigate.

Just in case, if you have it working, would you mind sharing your patch? You 
can just attach it to this jira.

      was (Author: karlpauls):
    Ah ok, you are talking about the normal FilePermission. Well, we don't do 
anything special with it so I was assuming it would be already doing what it 
should. I will investigate.

Just in case, if you have it working, would you might sharing your patch? You 
can just attach it to this jira.
  
> PermissionAdmin service can't handle java.ioFilePermission for "<<ALL FILES>>"
> ------------------------------------------------------------------------------
>
>                 Key: FELIX-1103
>                 URL: https://issues.apache.org/jira/browse/FELIX-1103
>             Project: Felix
>          Issue Type: Bug
>          Components: Conditional Permission Admin, Permission Admin
>    Affects Versions: felix-1.6.0
>            Reporter: Ulf Dittmer
>
> The PermissionAdmin service does not handle java.io.FilePermissions correctly 
> that use the special "<<ALL FILES>>" syntax for the path. It needs to be 
> special-cased in the 
> org.apache.felix.framework.security.util.Permissions.implies(Permission, 
> Bundle) method instead of being interpreted as a regular file name. I've 
> tested that it's sufficient to wrap all the name/postfix handling in a "if (! 
> "<<ALL FILES>>".equals(name)) { ... }" block.
> Affected Felix version is 1.4, because that's the last one that works with 
> PermissionAdmin service. It would affect Felix 1.6 as well if that could be 
> used at all (see bug Felix-1101).
> I'm not sure if this qualifies as a "Major" bug, but there's no easy 
> workaround (which the online docs say is what makes a "Minor" bug).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to