Re: padding error

Last question... I fixed the problem. The last issue was also my fault. I had changed the algorithm to DES when I was troubleshooting and for some reason it doesn't like algorithms under 128 bit. But I don't know why it didn't work previously. Why couldn't it find the provider at number 6? I'm n

Re: padding error

Ok, one more update. The last error was entirely my fault. I was searching for an element that didn't exist. But I'm still getting errors. Current configuration: BC provider at number 2. searching for text1 element. Still using j2se 1.4.2 This is the latest output and error: Data: DES Key encryp

Re: padding error

By the way, it's the same error when I put it as number one. If I use another app to list the providers it finds the BC provider fine. I removed the explicit "BC" from the getInstance calls. Now I get this error: Data: DES Key encryption key stored in file:/C:/SampleCode/XMLencrypt/testXMLenc/kek

Re: padding error

Ok, I placed the BC provider at number 2 and now I get this error: Data: DES Key encryption key stored in file:/C:/SampleCode/XMLencrypt/testXMLenc/kek [EMAIL PROTECTED] Key: [EMAIL PROTECTED] algorithmURI http://www.w3.org/2001/04/xmlenc#tripledes-cbc org.apache.xml.security.encryption.XMLEncryp

Re: padding error

[EMAIL PROTECTED] wrote: I did. It is number 6. From the stack trace, it seems like you are picking up Sun's JCE implementation, and not BouncyCastles. Are you using JDK 1.4? Sun's JCE implementation in 1.4 does not support the ISO10126Padding scheme. You need to upgrade to at least JDK 1.5

Re: RetrievalMethod in XMLDecrytion

I am not familiar with the RetrievalMethodResolver class - however if you wait until the next release of XMLSec (1.4), the JSR 105 API will be included and it allows you to create your own URIDereferencer implementation for resolving RetrievalMethod URIs (of any type). --Sean Julien TAUPIN wr

Re: AW: Using hardware provider for signing

config.xml is now independent of any provider configurations. The JCE provider search mechanism should find the appropriate provider for you given an algorithm. Vishal Liße, Jan (ext. Dienstleister) wrote: Hallo Vishal, I'm not sure if i fully understood the new concept. When i want to us

DO NOT REPLY [Bug 36532] - XML Security Requires FuncLoader.class, which has been removed from xalan 2.7.X

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

DO NOT REPLY [Bug 36526] - Out of memory error when signing or verifying big files

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

AW: Using hardware provider for signing

Hallo Vishal, I'm not sure if i fully understood the new concept. When i want to use a hardware provider i still need to configure it in config.xml, right? Where is the difference in how to integrate a hardware provider? Jan -Ursprüngliche Nachricht- Von: Vishal Mahajan [mailto:[EMAIL PR

Re: Using hardware provider for signing

Liße, Jan (ext. Dienstleister) wrote: Hallo, i have the requirement to sign data with a hardware provider (smart card). According to posts on this mailing-list the recommended way to integrate a hardware provider into xml-sec is by writing a SignatureAlgorithmSPI-Impl. and configuring this in c

RetrievalMethod in XMLDecrytion

Hi All   I work with java xmlsecurity 2.1.   I would like to know to get the EncryptedKey designed by in URI in a in RetrievalMethod element. The RetrievalMethod element is a child of a KeyInfo element, itself a child of an EncryptedData element.   The RetrievalMethodResolver allows only

Using hardware provider for signing

Hallo, i have the requirement to sign data with a hardware provider (smart card). According to posts on this mailing-list the recommended way to integrate a hardware provider into xml-sec is by writing a SignatureAlgorithmSPI-Impl. and configuring this in config.xml. But this approach lacks some f

AW: Problem with rsa decryption

Problem solved. It was my fault. After generating another 1024Bit RSA key pair everything works fine. -Ursprüngliche Nachricht- Von: Liße, Jan (ext. Dienstleister) Gesendet: Dienstag, 6. September 2005 19:18 An: 'security-dev@xml.apache.org' Betreff: Problem with rsa decryption Hi, i'm