[
https://issues.jboss.org/browse/AS7-2724?page=com.atlassian.jira.plugin.s...
]
Paul Gier updated AS7-2724:
---------------------------
Steps to Reproduce:
0. Create your own key if you don't have one
keytool -genkey -alias my-test-key
This will create a new key called "my-test-key" in the default keystore
location ~/.keystore
1. Build AS 7
2. Sign all jars in jboss dist directory with your new key ( find . -name
"*.jar" -exec jarsigner -storepass <yourpassword> '{}' my-test-key
\; )
3. Start the server in standalone or domain mode to see the signature errors on the
console.
was:
0. Create your own key if you don't have one
keytool -genkey -alias my-test-key
This will create a new key in the keystore location ~/.keystore
1. Build AS 7
2. Sign all jars in jboss dist directory ( find . -name "*.jar" -exec jarsigner
-storepass <yourpassword> '{}' my-test-key \; )
3. Start the server in standalone or domain mode to see the signature errors on the
console.
SecurityExceptions when starting server with signed jars
--------------------------------------------------------
Key: AS7-2724
URL:
https://issues.jboss.org/browse/AS7-2724
Project: Application Server 7
Issue Type: Bug
Components: Class Loading
Reporter: Paul Gier
Assignee: David Lloyd
There seems to be a problem when loading signed modules which causes the classloader to
think that the same packages are loaded with two different signatures. The issue seems to
be sporadic and will not always throw the exception for the same classes. I verified that
there was only a single jar containing the specified packages for several instances of the
error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira