DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43239>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43239





------- Additional Comments From [EMAIL PROTECTED]  2007-09-05 23:08 -------
(In reply to comment #5)
> This problem is due to an open bug in the JDK: see
> http://bugs.sun.com/view_bug.do?bug_id=4953555
> for more information.

Is the "javax.crypto.Cipher" class really used for verifying a Signature?  

> Since there is a workaround (use the correct key), 
> I would like to close this bug.

I don't agree. The problem occurs even if a new XMLSignature object is created
for each validation attempt (as you can see from the attached sample). IMHO, the
Apache XML Security library does never recover if the first validation attemt
for a RSA Signature is done against a DSA key. Afterwards, any validation attemt
for a RSA Signature against a RSA or DSA Key will fail. Therefore, the JVM has
to be restarted for recovering.

Why does the problem not occur if the Log4j log level is set to debug?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to