Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.
Trace:
Differences
This shows you the differences between two versions of the page.
|
linux:pine_gpg [2006/03/17 13:07] alien |
linux:pine_gpg [2007/01/15 09:49] (current) alien Changed X-GPG-PUBLIC_KEY and X-GPG-FINGRPRINT to: X-GPG-PUBLIC-KEY and X-GPG-FINGERPRINT since that looks more sane (and Lotus Notes does not like the underscore anyway) |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| * (Optionally - looks cool) add these custom X-Headers to each email you send with pine: <code> | * (Optionally - looks cool) add these custom X-Headers to each email you send with pine: <code> | ||
| # Add these customized headers (and possible default values) when composing | # Add these customized headers (and possible default values) when composing | ||
| - | customized-hdrs=X-GPG-PUBLIC_KEY: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA7 | + | customized-hdrs=X-GPG-PUBLIC-KEY: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA75CBDA0, |
| - | 5CBDA0, | + | X-GPG-FINGERPRINT: F2CE 1B92 EE1F 2C0C E97E 581E 5E56 AAAF A75C BDA0 |
| - | X-GPG-FINGRPRINT: F2CE 1B92 EE1F 2C0C E97E 581E 5E56 AAAF A75C BDA0 | + | |
| </code> You can edit ''~/.pinerc'' directly (look for the ''customized-hdrs='' line) or configure from within pine (**S**etup > **C**onfig > **W**hereis > ''customized-hdrs'')\\ Of course, the example GPG fingerprint and key-URL are mine, and you should substitute your own. | </code> You can edit ''~/.pinerc'' directly (look for the ''customized-hdrs='' line) or configure from within pine (**S**etup > **C**onfig > **W**hereis > ''customized-hdrs'')\\ Of course, the example GPG fingerprint and key-URL are mine, and you should substitute your own. | ||
| Line 67: | Line 66: | ||
| The decrypted message is displayed as a normal message. | The decrypted message is displayed as a normal message. | ||
| * //Note:// The plaintext is not saved to the mailbox. | * //Note:// The plaintext is not saved to the mailbox. | ||
| - | * //Note:// The above warning about //[[http://www.gnupg.org/documentation/faqs.html#q6.1|insecure memory]]// is caused by the fact that I am not running GPG as root, and the ''/usr/bin/gpg'' binary is not setuid root. If you're bothered by the warning, run ''chmod +s /usr/bin/gpg'' | + | * //Note:// The above warning about //[[http://www.gnupg.org/documentation/faqs.html#q6.1|insecure memory]]// is caused by the fact that I am not running GPG as root, and the ''/usr/bin/gpg'' binary is not setuid root. If you're bothered by the warning, implement either one of these solutions: |
| + | * run <code>chmod +s /usr/bin/gpg</code> to fix the use of insecure memory. or | ||
| + | * if you can't or don't want to install gpg setuid(root), then you can add the commandline parameter <code> | ||
| + | --no-secmem-warning | ||
| + | </code> to the gpg command, or put the line <code> | ||
| + | no-secmem-warning | ||
| + | </code> in your configuration file ''~/.gnupg/options'' or ''~/.gnupg/gpg.conf''. This will disable the warning message. | ||
| + | ==== PGP/Mime ==== | ||
| + | |||
| + | Pine Privacy Guard does not handle PGP/Mime encrypted emails. I found a couple of links with possible solutions, but have not yet looked too deeply into these. | ||
| + | |||
| + | * [[http://privacy.audiointuition.com/pine/ | Reading PGP/Mime messages with Pine]] | ||
| + | * [[http://www.david-guembel.de/index.php?id=12 | pgp-mime-handler]] | ||
