[
https://jira.jboss.org/jira/browse/JBCL-68?page=com.atlassian.jira.plugin...
]
Adrian Brock closed JBCL-68.
----------------------------
Resolution: Rejected
I'm closing this issue because there is no portable way to do this.
To take part in security debugging on the Sun JDK would require
access to the following in java.security.SecureClassLoader:
import sun.security.util.Debug;
private static final Debug debug = Debug.getInstance("scl");
The real fix to this problem would be in Sun's implementation to override and
log new ProtectionDomains in a SecureClassLoader::defineClass that takes
the ProtectionDomain.
VFSClassLoaderPolicy should support the security manager debug system
property
------------------------------------------------------------------------------
Key: JBCL-68
URL:
https://jira.jboss.org/jira/browse/JBCL-68
Project: JBoss ClassLoader
Issue Type: Sub-task
Reporter: Anil Saldhana
- access print all checkPermission results
- jar print jar verification information
- policy print policy information
- scl print permissions assigned by the SecureClassLoader
The access option has the following sub-options:
- stack include stack trace
- domain dump all domains in context
- failure dump the stack and domain that did not have permission before throwing the
exception
For example, to print all checkPermission results and trace all domains in context, set
java.security.debug to access,stack. To trace access failures, set it to access,failure.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira