DO NOT REPLY [Bug 40512] - Fix incompatible API changes to TransformSpi

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: Issues with verifying...

Raju, Prabhakar (P. ford.com> writes: > > > > > Hi, > > > I have an enveloped signature. If I try to verify, SignedInfo is verifying but failing in digest (reference) verification. Under root I have 4 objects (say A,B,C and signature). > > The transform clearly says 1) enveloped sigantur

RE: C++ - Moving to Automake

> My question - are there any objections to this being a 1.3.1? Or would > people prefer it to be 1.4 if the build has drastically changed? I distribute RPMs and packages, so I don't really care too much what it's called as long as the spec file works without modification on as many distros as p

Re[2]: Help: How to encrypt XML Element Data by Reference instead by Value

Dear Sean, Thank you very much for the help. Now I can't decrypt the content from XML file. I attach 2 files: 1. The encrypted file "CSDoc.woe.xml" 2. The original file "CSDoc.xml" The encryption steps are: SessionKey sessionKey = getSessionKey(); dataElement.setTextContent(getC

C++ - Moving to Automake

Hi all, For those that are interested, I am halfway through refactoring the UNIX build over to an automake based build. A few things are changing - in particular the build will now happen from the base directory of the package, rather than the src directory. I'm also now letting automake ha