diff options
| author | Stefan Monnier | 2010-10-15 17:55:33 -0400 |
|---|---|---|
| committer | Stefan Monnier | 2010-10-15 17:55:33 -0400 |
| commit | 0c747cb143fa227e78f350ac353d703f489209df (patch) | |
| tree | 5b434055c797bd75eaa1e3d9d0773e586d44daee /doc/misc/message.texi | |
| parent | a01a7932080e8a6e7bc8472c58cefabcc2c37df3 (diff) | |
| parent | aa095b2db98ae149737f8de00ee733b1d257ed33 (diff) | |
| download | emacs-0c747cb143fa227e78f350ac353d703f489209df.tar.gz emacs-0c747cb143fa227e78f350ac353d703f489209df.zip | |
Merge from trunk
Diffstat (limited to 'doc/misc/message.texi')
| -rw-r--r-- | doc/misc/message.texi | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/doc/misc/message.texi b/doc/misc/message.texi index ad56520f892..8e9eca55177 100644 --- a/doc/misc/message.texi +++ b/doc/misc/message.texi | |||
| @@ -1149,11 +1149,8 @@ If you have imported your old PGP 2.x key into GnuPG, and want to send | |||
| 1149 | signed and encrypted messages to your fellow PGP 2.x users, you'll | 1149 | signed and encrypted messages to your fellow PGP 2.x users, you'll |
| 1150 | discover that the receiver cannot understand what you send. One | 1150 | discover that the receiver cannot understand what you send. One |
| 1151 | solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set | 1151 | solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set |
| 1152 | @code{pgg-default-scheme} to @code{pgp}). If you do want to use | 1152 | @code{pgg-default-scheme} to @code{pgp}). You could also convince your |
| 1153 | GnuPG, you can use a compatibility script called @code{gpg-2comp} | 1153 | fellow PGP 2.x users to convert to GnuPG. |
| 1154 | available from | ||
| 1155 | @uref{http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You | ||
| 1156 | could also convince your fellow PGP 2.x users to convert to GnuPG. | ||
| 1157 | @vindex mml-signencrypt-style-alist | 1154 | @vindex mml-signencrypt-style-alist |
| 1158 | As a final workaround, you can make the sign and encryption work in | 1155 | As a final workaround, you can make the sign and encryption work in |
| 1159 | two steps; separately sign, then encrypt a message. If you would like | 1156 | two steps; separately sign, then encrypt a message. If you would like |