Mercurial > emacs
comparison man/pgg.texi @ 76288:2faf567bb62b
Fix typo.
| author | Chong Yidong <cyd@stupidchicken.com> |
|---|---|
| date | Sat, 03 Mar 2007 22:04:37 +0000 |
| parents | 613d36164fae |
| children | 52354deba43e |
comparison
equal
deleted
inserted
replaced
| 76287:1043dd3d5dd8 | 76288:2faf567bb62b |
|---|---|
| 270 different terminal from Emacs, with the @code{--keep-tty} option; this | 270 different terminal from Emacs, with the @code{--keep-tty} option; this |
| 271 tells @code{gpg-agent} use its own terminal to prompt for passphrases. | 271 tells @code{gpg-agent} use its own terminal to prompt for passphrases. |
| 272 | 272 |
| 273 When @code{gpg-agent} is not being used, PGG prompts for a passphrase | 273 When @code{gpg-agent} is not being used, PGG prompts for a passphrase |
| 274 through Emacs. It also has its own passphrase caching mechanism, | 274 through Emacs. It also has its own passphrase caching mechanism, |
| 275 which is controlled by the variable @code{pgg-read-passphrase} (see | 275 which is controlled by the variable @code{pgg-cache-passphrase} (see |
| 276 below). | 276 below). |
| 277 | 277 |
| 278 There is a security risk in handling passphrases through PGG rather | 278 There is a security risk in handling passphrases through PGG rather |
| 279 than @code{gpg-agent}. When you enter your passphrase into an Emacs | 279 than @code{gpg-agent}. When you enter your passphrase into an Emacs |
| 280 prompt, it is temporarily stored as a cleartext string in the memory | 280 prompt, it is temporarily stored as a cleartext string in the memory |