Raul Benito wrote:
Berin Lautenbach wrote:
- Yes I just checked it in.
Took me a while to find - I'm not too sure why, but the behaviour of
the canoncicaliser appears to have changed.
It appears that the canonicaliser is now storing it's output. So if
you re-use an instance, it will append the
Berin Lautenbach wrote:
- Yes I just checked it in.
Took me a while to find - I'm not too sure why, but the behaviour of
the canoncicaliser appears to have changed.
It appears that the canonicaliser is now storing it's output. So if
you re-use an instance, it will append the new canonicalisati
- Yes I just checked it in.
Took me a while to find - I'm not too sure why, but the behaviour of the
canoncicaliser appears to have changed.
It appears that the canonicaliser is now storing it's output. So if you
re-use an instance, it will append the new canonicalisation to the old
and retur
Berin,
Your fix has fixed this problem of duplicate data being outputted on
decryption. :-)
Thanks,
Vishal
Vishal Mahajan wrote:
2) This seems to be a regression in xml-security. Using (JDK1.4.2 +
BC) OR JDK1.5, the result of decryption in the sample seems incorrect.
The input to be encrypted w
