* What's this?
-EasyPG is a GnuPG interface for Emacs. It has two aspects: convenient
-tools which allow to use GnuPG from Emacs (EasyPG Assistant), and a
-fully functional interface library to GnuPG (EasyPG Library).
+EasyPG is an all-in-one GnuPG interface for Emacs. It has two
+aspects: convenient tools which allow to use GnuPG from Emacs (EasyPG
+Assistant), and a fully functional interface library to GnuPG (EasyPG
+Library).
+
+* Features
+
+The EasyPG Assistant provides the following features:
+
+- Keyring browser.
+- Cryptographic operations on regions.
+- Cryptographic operations on files.
+- Dired integration.
+- Encryption/decryption of *.gpg files.
+
+The EasyPG Library provides the following features:
+
+- The API covers most functions of GnuPG like GPGME.
+- S/MIME support using gpgsm.
+- Designed to avoid potential security pitfalls around Emacs
* Requirements
** GNU Emacs 21.4, XEmacs 21.4, or later
** GnuPG 1.4.3 or later
+ If you are using earlier versions, you will need to specify
+ --disable-gpg-test when ./configure.
* Quick start
(require 'epa-setup)
-Then you can browse your keyring by `M-x epa-list-keys'. In addition,
-you can do some cryptographic operations on dired.
+Restart emacs and type `M-x epa- TAB', and you will see a lot of
+commands available. For example,
+
+- To browse your keyring, type `M-x epa-list-keys'
+- To create a cleartext signature of the region, type `M-x epa-sign-region'
+
+You can also do some cryptographic operations from dired.
M-x dired
(mark some files)
PGG is outdated PGP library used by old Gnus (<= v5.11), MH-E, etc.
-There is a PGG backend written EasyPG called pgg-epg.el. However,
-EasyPG API is a superset of PGG and pgg-epg.el provides nothing but
-compatibility with PGG.
+There is a PGG backend written using EasyPG called pgg-epg.el.
+However, EasyPG API is a superset of PGG and pgg-epg.el provides
+nothing but compatibility with PGG.
+
+*** Limitations of PGG
-Limitations of PGG
+As I noted "PGG is outdated PGP library" above, PGG has several
+limitations. For example
-- PGG doesn't have a user interface to select keys for typical
- cryptographic operations
-- PGG can't handle messages signed with multiple keys correctly
-- PGG trusts any keys for encryption
+- PGG can't handle a message signed with multiple keys.
+- PGG can't prompt a user which key is being used.
+- PGG can't create a binary PGP messages.
+- PGG doesn't provide a way to select keys per cryptographic operation.
+- PGG ignores GnuPG's trust metrics.
** SEMI based MUA