[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

FYI, I solved the problem by using an encoding strategy similar the JVM's "convention" used for other permission "names".

I have to say though that that "convention" is quite gross.

Would that it were based on LDAP filter syntax ...

Thanks for the sanity checkÂguys,
- Ray


On Thu, Apr 18, 2013 at 2:02 PM, BJ Hargrave <hargrave@xxxxxxxxxx> wrote:
Then you probably have your own way to populate your PermissionCollections. However in Equinox which supports the OSGi permission specifications, the way to populate the PermissionCollections is via PermissionInfos which require the "0,1,2" constructors.

If you have special permissions that cannot have those sort of constructors, then you can't use the OSGi permissions specifications and will need to customize a framework implementation to use your own permission management model.
--

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the
OSGi Alliance
hargrave@xxxxxxxxxx





From: Â Â Â ÂRaymond Auge <raymond.auge@xxxxxxxxxxx>
To: Â Â Â ÂEquinox development mailing list <equinox-dev@xxxxxxxxxxx>
Date: Â Â Â Â2013/04/18 12:29
Subject: Â Â Â ÂRe: [equinox-dev] PermissionInfoCollection issues with perms cloning
Sent by: Â Â Â Âequinox-dev-bounces@xxxxxxxxxxx




PS: We were not loading our permissions from a standard policy file. Hence how we ended up with what we have.


On Thu, Apr 18, 2013 at 12:26 PM, Raymond Auge <raymond.auge@xxxxxxxxxxx> wrote:
Ok, I stand corrected. After looking at the code for PolicyParser it seems the 0, 1, 2 rule is indeed the case.

Other documentation seems to have implied that an arbitrary number of constructor arguments were acceptable:

http://docs.oracle.com/javase/6/docs/technotes/guides/security/crypto/CryptoSpec.html#AppA

However, I guess each of these different policy files must have it's own parser.

Sorry about my confusion.

- Ray

Thx


On Thu, Apr 18, 2013 at 12:05 PM, BJ Hargrave <hargrave@xxxxxxxxxx> wrote:
> Essentially the PermissionInfoCollection.addPermissions method
> attempts to create a "copy" of the permission for the purpose adding
> to it's collection.


Also, to be clear, there is no copying going on here. The code needs to construct a Permission object from the information in the PermissionInfo. The PermissionInfo contains the class name of the permission type with 0, 1 or 2 String arguments for the constructor. This very much the same as would be done by the Policy object to create permissions based upon the grant information in the policy file.
--

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the
OSGi Alliance
hargrave@xxxxxxxxxx


_______________________________________________
equinox-dev mailing list

equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev




--
Raymond Augà Â|ÂSenior Software Architect |ÂLiferay, Inc.Â

---
24-25 October 2012 |ÂLiferayÂSpain SymposiumÂ|Âliferay.com/spain2012
16 November 2012 |ÂLiferayÂItaly SymposiumÂ|Âliferay.com/italy2012




--
Raymond Augà Â|ÂSenior Software Architect |ÂLiferay, Inc.Â

---
24-25 October 2012 |ÂLiferayÂSpain SymposiumÂ|Âliferay.com/spain2012
16 November 2012 |ÂLiferayÂItaly SymposiumÂ|Âliferay.com/italy2012

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev




--
Raymond Augà Â|ÂSenior Software Architect |ÂLiferay, Inc.Â

---

24-25 October 2012 |ÂLiferayÂSpain SymposiumÂ|Âliferay.com/spain2012

16 November 2012 |ÂLiferayÂItaly SymposiumÂ|Âliferay.com/italy2012