It's actually even worse. It's not just specific parts of the
SignedData such as the encapsulated content info that are BER-encoded,
it seems as if any set or sequence is encoded using "constructed" and
infinite length. Thanks for the information, I'll try using the CMS
functions and see how far I
On Sat, Nov 06, 2010, Martin Bolet wrote:
> I just tested, whether the BER-encoding is preserved if I do not alter
> any of the contents. Unfortunately, it seems as if the encoding is not
> preserved. I did the following:
>
> d2i_PKCS7_bio(file, &p7);
>
> and then directly
>
> i2d_PKCS7_bio(fil
I just tested, whether the BER-encoding is preserved if I do not alter
any of the contents. Unfortunately, it seems as if the encoding is not
preserved. I did the following:
d2i_PKCS7_bio(file, &p7);
and then directly
i2d_PKCS7_bio(file2, p7);
again. "file" was BER-encoded using e.g. an Octet S
Thanks for this, I'll have a look at the streaming features then!
Best regards,
Martin
2010/11/6 Dr. Stephen Henson :
> On Fri, Nov 05, 2010, Martin Bolet wrote:
>
>> I'm sorry, I was not precise here. Actually I think (have to verify it
>> again though) the encoding is preserved if I parse the
>
On Fri, Nov 05, 2010, Anthony Gabrielson wrote:
> Hello, I think I know the answer to this, but I want to check in and verify.
> Does anyone know of capability that will allow me sign data with more than
> one key?
>
How do you want to sign the data? If you wish to use PKCS#7 or CMS then there
a
On Fri, Nov 05, 2010, Martin Bolet wrote:
> I'm sorry, I was not precise here. Actually I think (have to verify it
> again though) the encoding is preserved if I parse the
> EncapContentInfo and reencode it later on without changing the
> content.
>
> My problem was more the other way round: When
