Problems in encrypting with AES_192 and AES_256

Hi All, I'm trying to simply encrypt a simple XML file with the encryption sample available. org.apache.xml.security.samples.encryption.Encrypter; But I get the foollowning exception when I set the key size to 192 or 256 in the GenerateDataEncryptionKey() method. java.lang.SecurityException: Uns

Re: New Bee help required

Hi, For info about WSS4J you can try some of the link listed here [1]. Also wss4j-dev@ws.apache.org list is available for specific questions on WSS4J. Thanks, Ruchith [1] http://marc.theaimsgroup.com/?l=wss4j-dev&m=113877713719345&w=2 On 3/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >

Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Devs, I ran into an "java.security.SignatureException: object not initialized for verification" exception when trying to do sign and verify *twice* in the same thread, using different XMLSignature instances. I tracked this down to the use of "keysVerify" thread local tracker in org.apache.xml

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

ur explanation looks sound. What version of xmlsec are you using? Can you post a simple test case that triggers this error? Regards, Raul On 11/3/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Devs, > > I ran into an "java.security.SignatureException: object not > in

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

see > the problem. > Did the problem arise when you do something like this? > PrivateKey xk; PublicKey pk=xk.getPublickKey(); > XMLSignature s1=...; > XMLSignature s2=...; > s1.sign(xk); > s2.sign(xk); > s1.checkSignatureValue(pk); > > Or other kind of sequence? > Re

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

or performance improvements. A big +1 ! Can you raise a bug report in bugzilla, for proper tracking? will do. Thanks, Ruchith [1] http://rafb.net/paste/results/TYGEY793.html Regards, And thanks for finding the bug. On 11/4/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > H

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

> Can you raise a bug report in bugzilla, for proper tracking? will do. Done : http://issues.apache.org/bugzilla/show_bug.cgi?id=40896 Thanks, Ruchith -- www.ruchith.org

Re: Cannot sign-verify twice in the same thread with different XMLSignature instances

Hi Raul, thanks a lot for the quick fix ! Thanks, Ruchith On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: On 11/5/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Raul, > > On 11/5/06, Raul Benito <[EMAIL PROTECTED]> wrote: > > You Wss4j guy a

Re: VOTE: Apache XML Security Java Library 1.4 Release

Hi Raul, I just discovered some more signature faliures in WSS4J with the latest XML-Sec SVN HEAD :-(. at the first glance it seems like an issue with C14N ... please give me a few more hours I will try to pin point the issue ... maybe an issue with WSS4J itself . Thanks, Ruchith On 11/13/06, R

Re: VOTE: Apache XML Security Java Library 1.4 Release

false alarm ... million apologies ! ... its early morning over here in Sri Lanka :-) Was using the wrong constructor ! All WSS4J unit tests passes with the latest xml-sec svn HEAD. Thanks, Ruchith On 11/16/06, Ruchith Fernando <[EMAIL PROTECTED]> wrote: Hi Raul, I just discovered som

Signature verification fails due to Java object reference mismatch in ElementProxy#guaranteeThatElementInCorrectSpace()

Hi Devs, ElementProxy#guaranteeThatElementInCorrectSpace() method contains the following check : if ((namespaceSHOULDBE!=namespaceIS) || !localnameSHOULDBE.equals(localnameIS) ) { Object exArgs[] = { namespaceIS +":"+ localnameIS, namespaceSHOULDBE +":"+ localnameSHOUL

Re: Signature verification fails due to Java object reference mismatch in ElementProxy#guaranteeThatElementInCorrectSpace()

mespaces. Anyway I'm working in plug-able corrects in order to change this behavior even disable it. Regards, On 7/15/07, Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi Devs, > > ElementProxy#guaranteeThatElementInCorrectSpace() method contains the > following

xmlsec-1.4.1.jar in m2 repo

Hi Devs, Can we please add xmlsec-1.4.1.jar to this [1] location. I think the xmlsec-1.4.1.jar will have to be signed and the signature file (xmlsec-1.4.1.jar.asc) and md5 digest file (xmlsec-1.4.1.jar.md5) will have to be included in the same dir. The Apache Rampart project is waiting for this

Re: Controlling placement of in result XML tree

Hi, If you are planning to sign the message the standard [1] way then you will have to place the "Signature" element in the "Security" header of the SOAP message. The WS-Sec spcefication describes how to encrypt and/or sign the message while preserving SOAP envelop structure. You can do this usin

Re: Java XMLSec 1.4.2 Release

Hi Sean, Can we please have the xmlsec-1.4.2.jar in the maven repo. (It should go into a 1.4.2 directory here [1]) ? This will really help projects like Apache WSS4J and Apache Rampart that use maven2 build system. Thanks, Ruchith 1. http://people.apache.org/repo/m2-ibiblio-rsync-repository/org