Welcome to the new location of Alien's Wiki, sharing a single dokuwiki install with the SlackDocs Wiki.
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revisionLast revision | |||
— | linux:pine_gpg [2006/05/29 09:45] – alien | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Email encryption with Pine and GPG ===== | ||
+ | Pine is a nice but powerful console mail client, and just like GPG, it is available on many Linux and Unix based computers. | ||
+ | It is not hard to make [[http:// | ||
+ | |||
+ | ==== Installation and configuration ==== | ||
+ | |||
+ | * Install //Pine Privacy Guard// on your computer: < | ||
+ | wget http:// | ||
+ | tar -C /usr/local -zxvf pinepg-1.02.tgz | ||
+ | cd /usr/local/ | ||
+ | chown -R root:root / | ||
+ | ln -s pinepg-1.02 pinepg | ||
+ | chmod 755 / | ||
+ | </ | ||
+ | |||
+ | * Uncomment the line '' | ||
+ | # | ||
+ | default-recipient-self | ||
+ | </ | ||
+ | |||
+ | * Configure Pine's display-filters and sending-filters\\ either edit your '' | ||
+ | # This variable takes a list of programs that message text is piped into | ||
+ | # after MIME decoding, prior to display. | ||
+ | display-filters=_LEADING(" | ||
+ | _LEADING(" | ||
+ | |||
+ | # This defines a program that message text is piped into before MIME | ||
+ | # encoding, prior to sending | ||
+ | sending-filters=/ | ||
+ | / | ||
+ | </ | ||
+ | |||
+ | * (Optionally - looks cool) add these custom X-Headers to each email you send with pine: < | ||
+ | # Add these customized headers (and possible default values) when composing | ||
+ | customized-hdrs=X-GPG-PUBLIC_KEY: | ||
+ | X-GPG-FINGRPRINT: | ||
+ | </ | ||
+ | |||
+ | ==== Working with GPG in Pine ==== | ||
+ | |||
+ | === Sending email === | ||
+ | |||
+ | You use Pine as usual, so composing a new email is no different than before. The fun starts when you press < | ||
+ | |||
+ | - Unfiltered; send email without using any cryptography. | ||
+ | - Encrypt the email (PinePG will also sign it by default). | ||
+ | - Clear-sign the email. | ||
+ | |||
+ | After entering your choice, the email is sent. | ||
+ | |||
+ | During your Pine session, the first time you have to use GPG to read or send a mail message, you will be prompted for your GPG passphrase. After that PinePG will [[http:// | ||
+ | |||
+ | === Receiving email === | ||
+ | |||
+ | If you open any email that contains a GPG signed or encrypted message, the pinepg filter is automatically invoked. You are prompted for your GPG passphrase, so that the message can be decrypted. The caracters that you type, will not be displayed on the screen.\\ | ||
+ | The output of GnuPG is displayed. It will show whether or not the encrypted text was successfully decrypted, if the GPG signature is valid if it was signed, and any other relevant information: | ||
+ | < | ||
+ | gpg: WARNING: using insecure memory! | ||
+ | gpg: please see http:// | ||
+ | gpg: Signature made Fri Mar 17 03:19:07 2006 PST using DSA key ID A75CBDA0 | ||
+ | gpg: Good signature from "Eric Hameleers <alien slackware.com>" | ||
+ | gpg: aka "Eric Hameleers <alien sox.homeip.net>" | ||
+ | </ | ||
+ | Press '' | ||
+ | The decrypted message is displayed as a normal message. | ||
+ | * //Note:// The plaintext is not saved to the mailbox. | ||
+ | * //Note:// The above warning about // | ||
+ | * run < | ||
+ | * if you can't or don't want to install gpg setuid(root), | ||
+ | --no-secmem-warning | ||
+ | </ | ||
+ | no-secmem-warning | ||
+ | </ | ||
+ | |||
+ | |||
+ | ==== 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:// | ||
+ | * [[http:// |