gards,
Werner
> -Ursprüngliche Nachricht-
> Von: Vishal Mahajan [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 11. Februar 2004 13:31
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: AW: Problem in Decryption
>
>
> Dittmann,
>
> I am in sync with you as fa
: AW: Problem in Decryption
Hi Dittmann,
Dittmann Werner wrote:
Vishal, Berin
during some encrypt/decrypt tests with signature:
This is mainly a problem for "content" mode encryption.
AFAIK, during encryption XMLCipher creates a document fragment
with the content, serializes and e
> -Ursprüngliche Nachricht-
> Von: Vishal Mahajan [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 11. Februar 2004 12:33
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Problem in Decryption
>
>
> Hi Dittmann,
>
> Dittmann Werner wrote:
>
> >Vishal, B
ontent mode.
Regards,
Werner
-Ursprüngliche Nachricht-
Von: Vishal Mahajan [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 11. Februar 2004 08:35
An: [EMAIL PROTECTED]
Betreff: Re: Problem in Decryption
Hi Berin,
I agree with your reading of the spec. But, the spec does not prevent
the en
Vishal Mahajan wrote:
It could be useful to have an API that you mention. But the question is
what does "element content" mean in the spec, and we definitely should
have an API to support encryption (and of course decryption) of that
"element content".
At the moment, the API exists - but it ass
with Signature/Encrypt.
During our test we already did tests signature/encryption
in content mode.
Regards,
Werner
-Ursprüngliche Nachricht-
Von: Vishal Mahajan [mailto:[EMAIL PROTECTED] Gesendet:
Mittwoch, 11. Februar 2004 08:35
An: [EMAIL PROTECTED]
Betreff: Re: Problem in Decryption
Hi
our test we already did tests signature/encryption
in content mode.
Regards,
Werner
-Ursprüngliche Nachricht-
Von: Vishal Mahajan [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 11. Februar 2004 08:35
An: [EMAIL PROTECTED]
Betreff: Re: Problem in Decryption
Hi Berin,
I agree with your read
Vishal,
I ran accross this when I was doing the checks for the Merlin Interop
examples - which have white space prior to the EncryptedData node, even
when that node is of type "element content". According to the spec (from
section 4.2) :
#
"The decryptor SHOUL
Correction. The document I wanted to quote from the spec is this:
A23B45C56
Thanks,
Vishal
Vishal Mahajan wrote:
Hi Berin,
I agree with your reading of the spec. But, the spec does not prevent
the encrypter from putting whitespaces between the tags o
Regards,
Werner
> -Ursprüngliche Nachricht-
> Von: Vishal Mahajan [mailto:[EMAIL PROTECTED]
> Gesendet: Mittwoch, 11. Februar 2004 08:35
> An: [EMAIL PROTECTED]
> Betreff: Re: Problem in Decryption
>
>
> Hi Berin,
>
> I agree with your reading of the spe
Hi Berin,
I agree with your reading of the spec. But, the spec does not prevent
the encrypter from putting whitespaces between the tags of EncryptedData
and its parent node. Also there are example encrypted documents like the
following in the spec:
A23B45C56
Hi All,
I think there is a problem in the decryption process of the XMLCipher
class. To put the problem across, here's my question:
If there is some whitespace between the tags of EncryptedData and its
parent (See the example below) and the Type attribute of the
EncryptedData corresponds to "e
12 matches
Mail list logo