Hi Charly, thank you for your answer.
> I don't know of any software conflict when signing an e-mail using both > OpenPGP/MIME and S/MIME, although that possibility had been raised in > GPGMail's forum around 2003. That's the point. There seems to be software issues but I'm not sure right know what the exact problem is. > I have found multiple references that preclude using both PGP/MIME > (that's not OpenPGP/MIME) and S/MIME. > PGP/MIME refers to PGP Corporation, now a part of Symantec. Not sure about that. Nowhere in RFCs 2015, 3156 or 5581 the term "_____/MIME" is introduced. Only RFC 4880 mentions "OpenPGP/MIME" once. On the contrary it defines that OpenPGP must use the content types "application/pgp-encrypted", "application/pgp-signature" and "application/pgp-keys". Best regards, Alex On 26.01.2011, at 10:31, Charly Avital wrote: > Alexander Willner wrote the following on 1/26/11 2:28 AM: >> I'm usually using OpenPGP/MIME together with S/MIME. Can you elaborate >> exactly in which cases they don't play well together? > > In order to learn more about github and S/MIME I have found the following: > <https://github.com/GPGMail/GPGMail/wiki/Old-Todo-List> > > You might be interested in: > <http://luxsci.com/blog/installing-smime-and-pgp-encryption-certificates-into-major-email-clients.html>. > > If this long URL causes problems, try using its TinyURL equivalent: > <http://tinyurl.com/nknrpj> > > The following post on the Enigmail forum covers quite extensively > OpenPGP/MIME and S/MIME, although it does not focus on your question > "...they don't play well together?" > <http://mozilla-enigmail.org/forum/viewtopic.php?t=67?> > > I don't know of any software conflict when signing an e-mail using both > OpenPGP/MIME and S/MIME, although that possibility had been raised in > GPGMail's forum around 2003. > > I have found multiple references that preclude using both PGP/MIME > (that's not OpenPGP/MIME) and S/MIME. > PGP/MIME refers to PGP Corporation, now a part of Symantec. > > In a very simplistic way, S/MIME seems "easier" to implement, because it > does not require the installation (and updating) of a cryptographic > system like GnuPG. It requires the user to obtain a certificate (a "key" > in OpenPGP parlance) from a CA, and to import that certificate in the > user's S/MIME capable e-mail client or browser (easier said than done, > but doable all the same). > > Free certificates are valid for one year, then the user has to apply for > a new certificate. Paid-for certificates may have extended validity. > > I have Alex's S/MIME certificate in my Keychain Access utility, part of > the MacOSX installation. > > The use of either or both protocols is up to the user's decision. > > I use OpenPGP/MIME, when required. > > Charly > > > > > > > > > >
smime.p7s
Description: S/MIME cryptographic signature
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ gpgtools-users mailing list [email protected] Changes: http://lists.gpgtools.org/mailman/listinfo/gpgtools-users Unsubscribe: http://lists.gpgtools.org/mailman/options/gpgtools-users/[email protected]?unsub=Unsubscribe&unsubconfirm=1 This email sent to: [email protected]
