Christian Weber wrote: > > Dear folks, > > on the manpage for smime you can find under "BUGS": > > >The code currently will only write out the signer's certificate > >to a file: if the signer has a separate encryption certificate > >this must be manually extracted. There should be some heuristic > >that determines the correct encryption certificate. > > OK so far, but where is the certificate within an enveloped message? > Given a signer with a separate encryption certificate, where does > he have to put it in? According to PKCS#7 there is no area for > envelopers public encryption key. The envelope itself just contains > recipient infos (issuer and serial) for each recipient (whereas > the signer may be one of). Still the cert ist not within the > message. > > Does anyone know where to leave the public encryption cert within > the message if it is different from signature cert? > The certificate isn't in an enveloped message its in the signed message. There are various rules for finding the encryption certificate (if it isn't the same as the signing certificate) these are described in for example RFC2633. > BTW: We didnt manage to gather information about the nature of > supported encrypted data. Is it usual to add the data with other > content types than plain text or base64-encoded streams, eg > zip-compressed data? > Its can be an abrbitrary data but it will typically be in MIME format, the text/plain stuff is just there for convenience. However processing the decrypted data is up to the application. Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Celo Communications: http://www.celocom.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
