I wrote: > Looking at compose.c in 1.4.1 (which I presume is similar to 1.4), I > see that it uses PGP_SECRING where 1.5.4 uses PGP_PUBRING. > > Now I'm curious to know why that was changed. To the ChangeLogs... So this was changed with a checkin to add S/MIME support. I can't tell why this would need to be changed (or what it has to do with S/MIME :). Perhaps someone more in the know can enlighten me as to whether this was an intentional change or something that slipped in by accident. http://cvs.gnupg.org/cgi-bin/viewcvs.cgi/mutt/compose.c.diff?r1=3.0&r2=3.1&cvsroot=Mutt -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== Any sufficiently advanced technology is indistinguishable from a rigged demo
Attachment:
pgpJqRWtN8WUs.pgp
Description: PGP signature