On Tue, Jan 08, 2008, rfx wrote: > Thank you > > Exactly, i compare ASN1 signeddata structure ver 1.5 of openssl signing > using "smime" function and a CMS ASN1 structure ... and it seem ??? to be > different only at the introducing "data" by a "OCTETSTRING" after "OBJECT > :pkcs7-data" ... > > Is it possible to introduce "data" at the good offset using asn1parse > function of openssl ? ... other method ? > This difference is alone ? >
The data after the OCTETSTRING is the content being signed passed using the -in command line switch to the OpenSSL smime utility. So if you include the correct content and sign with the correct key/certificate it should be acceptable. You can't use the asn1parse utility to change the OCTETSTRING on an existing structure. It wouldn't help if you could because that structure contains a digital signature later on and if you changed the content the signature would no longer be valid. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
