Gang, I have just realized that we probably need to become more security concerned than we have been so far.
I think the situation can be explained as; * Qi4j will require AllPermissions or very very near that. * Client code uses Qi4j, so its ProtectionDomain will rule. * If client code is not granted AllPermissions, then Qi4j will not run. So, in an effort to allow Qi4j to operate in secured environments, I will start look into where we will need to create the security context boundaries. In essence, it means that we will need to put in PrivilegedActions (if SecurityManager is present) whereever the client code enters into the Qi4j runtime. The time frame for completing this is NOT pre-1.0, but something like 1.1 or even a 1.2, so no rush to panic. Step two is to also define the Permissions that are Qi4j specific. And this will take a while, hence starting discussion now. First up; Shall we base all permissions on the java.security.BasicPermission? For those not familiar, BasicPermission is used when you have a "tree" of something, you can indicate "what" from any node and down. See javadocs for details. Anyone has any thoughts on this topic? Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
