[
https://issues.jboss.org/browse/JBESB-3673?page=com.atlassian.jira.plugin...
]
David Tucker commented on JBESB-3673:
-------------------------------------
I appreciate the help. I will say that I know the solution to JBAOP-163 and it was to
release a patch with cglib unsigned for EAP 5.1. I'm investigating some other avenues
because even if we are willing to unsign a jar on a case by case basis, it seems that
isn't a good solution in the long term. My preferred solution would be to tell the
JVM to ignore the signatures.
jbossesb-rosetta.jar is signed
------------------------------
Key: JBESB-3673
URL:
https://issues.jboss.org/browse/JBESB-3673
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: David Tucker
Currently the jbossesb-rosetta.jar contains signing files. This has the potential to
create issues if the keys do not match each other. I discovered this when I was trying to
instrument some classes for AOP that are contained in the jar. I kept running into a
java.lang.SecurityException for any classes contained in the rosetta jar and eventually
discovered that signature files were the source of the issue. Removing the RSA and RF
files from the archive would solve this issue for AOP.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira