You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2018/08/24 21:24:00 UTC

[jira] [Resolved] (FELIX-5917) [Fwk security] Fix BundlePermission check for fragments

     [ https://issues.apache.org/jira/browse/FELIX-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved FELIX-5917.
-------------------------------
       Resolution: Fixed
    Fix Version/s: framework-6.0.2

I think I found it. Basically, it looks like we are using the wrong symbolic-name when we construct the BundlePermission to check for (namely, the one of the fragment instead of the host). 

Should be fixed in r1838966. Could you please try it with 6.1.0-SNAPSHOT and see if that makes it work for you and otherwise, reopen this issue?

Thanks a lot!

> [Fwk security] Fix BundlePermission check for fragments
> -------------------------------------------------------
>
>                 Key: FELIX-5917
>                 URL: https://issues.apache.org/jira/browse/FELIX-5917
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework Security
>         Environment: Framework 6.0.0 + Fwk security 2.6.0
>            Reporter: Christoph Nölle
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: framework-6.0.2
>
>
> With the current framework a fragment seems to require
> (org.osgi.framework.BundlePermission "*" "fragment")
> to attach to a host, instead of the expected and more restrictive
> (org.osgi.framework.BundlePermission "<host-symbolic-name>" "fragment")
> I have tested with Equinox as well, to make sure the provided symbolic name is correct etc., then it works as expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)