[
https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s...
]
Alvin Thompson edited comment on AS7-6068 at 12/19/12 12:04 PM:
----------------------------------------------------------------
Test case? Add a security provider jar to your war/ear and attempt to use it. I used
bouncycastle but I imagine it doesn't make a difference. Before the security provider
can load, the jar needs to be validated. This is done by accessing the files through the
jar file system (provided by jboss) and inspecting them (I imagine it does something like
comparing the file's checksum to a known value). Apparently, the jar file system does
not properly handle the "jar within a jar" scenario. Please look at the related
bug for details.
was (Author: alvint):
Test case? Add a security provider jar to your war/ear and attempt to use it. I used
bouncycastle but I imagine it doesn't make a difference. Before the security provider
can load, the jar needs to be validated. This is done by accessing the files through the
jar file system (provided by jboss) and inspecting them (I imagine it does something like
comparing the file's checksum to a known value). Apparently, the jar file system does
not properly handle the "jar within a jar" scenario.
jar file system is broken again (regression)
--------------------------------------------
Key: AS7-6068
URL:
https://issues.jboss.org/browse/AS7-6068
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Alvin Thompson
Assignee: JBoss SET
Priority: Critical
Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because
JBOSS's jar file system becomes confused when there are JARs nested in other
JARs/WARs/EARs, which is pretty much always.
This was supposedly fixed in previous versions, but it's back in 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira