Hi,
I'm a newbie in xml signature. I have look at the example :
templatesign in order to sign a xml file with a key in a PEM file but
i have the error : could not find node
I don't undestand why a node is requiered because my first
file can't have this node.
In the future i would like to m
Brent Putman wrote:
The real test would be if you get different behavior from this:
Cipher xmlEncCiperAES = Cipher.getInstance("AES/CBC/ISO10126Padding", "BC");
versus this:
Cipher xmlEncCiperAES = Cipher.getInstance("AES/CBC/ISO10126Padding");
If the first works, but the latter doesn't (t
ok that's good for you but nobody can help me about my xml signature ?
Thanks
Brent Putman wrote:
>
>
>
> [EMAIL PROTECTED] wrote:
>>
>> Very helpful information guys, thanx...
>>
>> I am using bouncycastle, which should handle ISO10126 padding even in
>> 1.4 though, right?
>
> Yes, I bel
[EMAIL PROTECTED] wrote:
Very helpful information guys, thanx...
I am using bouncycastle, which should handle ISO10126 padding even in
1.4 though, right?
Yes, I believe so, although I haven't tried it. But that's the whole
point of the extensible security provider framework.
The issue
DEBUG: Provider=SunJCE version 1.42:AES
...
This list is the same in 1.4 and 1.5 traces.
Edward Thompson
Sean Mullan <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
08/11/2008 04:27 PM
Please respond to
security-dev@xml.apache.org
To
security-dev@xml.apache.org
cc
Subject
Re: JCEID to
Brent Putman wrote:
The JCEID algorithm identifier gets looked up by the relevant security
provider class (e.g. Cipher), and is based on all 3 parameters: the
cipher, mode and padding.
This is highly platform vendor and version specific but as far as I
remember, support for the ISO10126 paddi
The JCEID algorithm identifier gets looked up by the relevant security
provider class (e.g. Cipher), and is based on all 3 parameters: the
cipher, mode and padding.
This is highly platform vendor and version specific but as far as I
remember, support for the ISO10126 padding for XML Encryption
