Re: CAPICOM BUG?

From: Kaare Langedrag (kare.langedrag_at_ergo.no)
Date: 09/26/03 

Date: Fri, 26 Sep 2003 08:58:16 +0200

I use the default .NET marshaling with C#.

I have read about the known issue and i have tried to envelop both odd an
even byte-count messages with no problem (as long as they are quite large).
The problem is when i try to envelop small files. I have not managet to sign
any files, whatever the size and odd/even count of the input is.

"Michel Gallant" <neutron@nspxistar.ca> wrote in message
news:u8vJUO3gDHA.2576@TK2MSFTNGP11.phx.gbl...
> Not sure what the problem is. There IS a known issue with
> COM marshaling interop in .NET (having to do with
> COM bstr --> managed Unicode string and chopping odd
> byte-count data in using ByteArrayToBinaryString.
>
> I have used CAPICOM with VBScript and ByteArrayToBinaryString
> and have seen no limitations on data size, small or large.
>
> What language are you using?
>
> - Michel Gallant
> MVP Security
>
> "Kåre Langedrag" <kare.langedrag@ergo.no> wrote in message
> news:fe5d01c38338$61192170$a601280a@phx.gbl...
> >
> > 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?
> >
> >
>
>