[
https://jira.jboss.org/jira/browse/JBAS-4154?page=com.atlassian.jira.plug...
]
Anil Saldhana commented on JBAS-4154:
-------------------------------------
I am not interested in injecting any custom policy implementation just to handle vfs urls.
We cannot ignore the fact that JDK implementations differ by vendors and also by
versions.
Get the server to run under a security manager
----------------------------------------------
Key: JBAS-4154
URL:
https://jira.jboss.org/jira/browse/JBAS-4154
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Security
Affects Versions: JBossAS-5.0.0.Beta1
Reporter: Scott M Stark
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.0.0.GA
The testsuite tests-security-manager target was failing due to the aop layer not creating
classes with correct ProtectionDomains. This is fixed in (JBAOP-368). The next problem is
that the server.policy needs to use vfsfile urls for the permission assignments. However,
because these are URLs and not URIs, there has to be a URL handler available when the
policy is read at bootstrap. Currently a policy entry like:
grant codeBase "vfsfile:${jboss.home.dir}/lib/-" {
permission java.security.AllPermission;
};
fails because the jboss vfsfile URL handler is unknown:
policy: Adding policy entry:
policy: signedBy null
policy: codeBase vfsfile:/tmp/trunk/build/output/jboss-5.0.0.Beta2/lib/-
java.security.policy: error adding Entry:
java.net.MalformedURLException: unknown protocol: vfsfile policy:
--
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