DSIGReference class

Title: DSIGReference class     I've run into strange things in DSIGReference class: 1. There is errStr variable of safeBuffer type declared in hashReferenceList(), but never used. It is used to keep the text "Reference URI="myReference" failed to verify\n", but then this variable is no

Re: DSIGReference class

Milan Tomic wrote: I've run into strange things in DSIGReference class: 1. There is errStr variable of safeBuffer type declared in hashReferenceList(), but never used. It is used to keep the text "Reference URI="myReference" failed to verify\n", but then this variable is not used in any

Re: Detached signature - reference (URI) coding.

Andrzej, I *think* this is a bug, but I'm open to suggestions. I suspect the library should convert back to local code page? But what happens if the filename on disk is in UTF-8? Open to suggestions on this one :>. Cheers, Berin Andrzej Matejko wrote: Hi, Problem: How to encode non-asc

With comments

Title: With comments     Does C++ XSEC libraries support cannonicalization WithComments? I have one document signed and verified using Java XSEC libraries, but I can't verify it using C++ XSEC libraries. Reference digest is not valid. Here is SignedInfo: http://www.w3.org/TR/2001/REC-

RE: ThreeSignerContract example -- detached signatures examples?

Hi Dave, Let me respond to your questions. I'll extract them: Question: "Why is the Id attribute unworkable? For example, if I use a string GUID for the Id, would that work then? Each element in our system actually has such a unique id already (for primary key), though it's meaningless to peopl

Re: ThreeSignerContract example -- detached signatures examples?

Thanks, Blake. I certainly have a much better understanding after your clarifications, examples and tips. You "da man!" Many thanks. Regarding this one comment of yours: > XML Signatures are slow because XML processing is slow. There are just no > two ways about it. 90 percent of the processin

RE: ThreeSignerContract example -- detached signatures examples?

Hi Dave, XML signature, as realized by the W3C XML Signature Recommendation, is quite inefficient, but not because of specific design decisions in the standard(with exception of XPath Filter 1.0), but because of the requirements for canonicalization as well as the power of XML Signature to authent

[EMAIL PROTECTED]: xml-security/xml-security failed

--- To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org:8080/gump/xml-security/xml-security/rss.xml Atom: http://brutus.apache.org:8080/gump/xml-security/xml-security/atom.xml -- Produced by Gump 2.0.3-alpha-0002. [Run (20040623 09:00:07, brutus:brutus-public:20040623 09:00:07)] http://brutus.apache.org:8080/gump/index.html http://brutus.apache.org:8080/gump/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus]

[GUMP@brutus]: xml-security/xml-security failed

--- To subscribe to this information via syndicated feeds: RSS: http://brutus.apache.org:8080/gump/xml-security/xml-security/rss.xml Atom: http://brutus.apache.org:8080/gump/xml-security/xml-security/atom.xml -- Produced by Gump 2.0.3-alpha-0002. [Run (20040623 09:00:07, brutus:brutus-public:20040623 09:00:07)] http://brutus.apache.org:8080/gump/index.html http://brutus.apache.org:8080/gump/options.html -- Apache Gump http://gump.apache.org/ [Instance: brutus]

Re: Problem with c14n

The fix looks good. All tests pass including the one that reproduced the problem. I have checked-it-in. Thanks, Vishal Raul Benito wrote: > > Vishal Mahajan wrote: > > >Attached is the testcase that shows the problem. I'll check-in the test into the > >workspace later. > > > >Vishal > > > >Be