CAPICOM BUG?

From: K蚌e Langedrag (kare.langedrag_at_ergo.no)
Date: 09/25/03 

Date: Thu, 25 Sep 2003 00:41:06 -0700

I have tried to create signeddata and envelopeddata on
binary content.

I use the function Utilities.ByteArrayToBinaryString in
order to insert a binary byte-array into the signeddata
and envelopeddata objects content properties.

When i put relatively large amounts of data into the
signeddata object i can manage to create enveloped data.

The problem is that when i use small amounts of data-input
the output data (enveloped data) allways has as1 parsing
error...

Whatever data i insert into signeddata i allways get asn1
error on the output...

If i input pure text as a string, or if i base64 encode
the data everything works, but this is not what i want.

Does anyboy know binary data only works on large files in
envelopeddata?

Relevant Pages

  • Re: CAPICOM BUG?
    ... COM bstr --> managed Unicode string and chopping odd ... > order to insert a binary byte-array into the signeddata ... > and envelopeddata objects content properties. ... > The problem is that when i use small amounts of data-input ...
    (microsoft.public.platformsdk.security)
  • Re: CAPICOM BUG?
    ... It uses CAPICOM to Envelop or Sign, using CAPICOM, and local ... > order to insert a binary byte-array into the signeddata ... > and envelopeddata objects content properties. ... > The problem is that when i use small amounts of data-input ...
    (microsoft.public.platformsdk.security)
  • Re: CAPICOM: How to check the validity of certificate when verifiing the signature fails?
    ... I think the folks who architected CAPICOM were a tad conservative ... the objects must successfully pass Verify or Decrypt before ... you can decode a CMS/PKCS #7 SignedData or EnvelopedData ...
    (microsoft.public.platformsdk.security)