Re: Invalid Reference Signature when I try to refer some XMLObject element

It is very interesting how is solved this problem in the other XAdES realizations? Maybe they use another XML Security library like BouncyCastle? Are there some plans for JDK and Apache XML Security to provide all kind of functionality which exists in BouncyCastle and similar libraries? In this w

Re: Invalid Reference Signature when I try to refer some XMLObject element

For XML Signature I use JDK6. For XML Encription I use Apache XML Security 1.4. If this will solve my problem I will use Apache XML Security for both. On 1/31/07, Sean Mullan <[EMAIL PROTECTED]> wrote: Miroslav Nachev wrote: > I will try your suggestions tomorrow, but I am not sure that this i

Re: Invalid Reference Signature when I try to refer some XMLObject element

Miroslav Nachev wrote: I will try your suggestions tomorrow, but I am not sure that this is the problem. Before to quit from the office I found that the digest value for this reference is different calculated for Signing and Validation. The stack trace from Exception is missing because any exc

Re: Invalid Reference Signature when I try to refer some XMLObject element

I will try your suggestions tomorrow, but I am not sure that this is the problem. Before to quit from the office I found that the digest value for this reference is different calculated for Signing and Validation. The stack trace from Exception is missing because any exception is not thrown. The

Re: Invalid Reference Signature when I try to refer some XMLObject element

Miroslav Nachev wrote: Hi, I need of help to find where is my mistake during signing process. The case is: I would like to sign some element which is part of "This element is located in "" as sub-element named . During signing process everything is OK, but when I try to verify the signature, t

Re: Multiple digests of the same resource

I've looked into this a bit further now, and can make some more informed comments. The biggest problem with this suggestion is that the XMLSec API does not expose sufficient information to reason about whether a given nested manifest can be skipped or not. That is, if you look at the verify code

Invalid Reference Signature when I try to refer some XMLObject element

Hi, I need of help to find where is my mistake during signing process. The case is: I would like to sign some element which is part of "This element is located in "" as sub-element named . During signing process everything is OK, but when I try to verify the signature, the result is "Bad refer

DO NOT REPLY [Bug 41510] New: - org.apache.xml.security.keys.content.KeyValue.getPublicKey() returns null for DSA key

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: Error allocating memory

Can you send me a copy of the signature XML that you are verifying? The -x kicks in the interop resolver. But it should definitely not give an out of mem error. Cheers, Berin Travis Reid wrote: I am currently using the xml-security-c 1.3.1 library to check a signature I created usin

Error allocating memory

I am currently using the xml-security-c 1.3.1 library to check a signature I created using the java xml security library. I have built the library without xalan-support. I have references ( relative URI's) in a manifest object of the signature. I am expecting to write my own resolver to resolve t