* What's this?
-EasyPG is yet another GnuPG interface for Emacs. It consists of two parts:
-
-- "The EasyPG Assistant" which provides basic GUI of GnuPG
-- "The EasyPG Library" which enables use of various features of GnuPG
-
-NOTE: EasyPG is neither a fork nor a re-implementation of Gnus/PGG.
+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).
* Requirements
M-x dired
(mark some files)
- : e (or M-x epg-dired-do-encrypt)
- (select recipients and click [OK])
+ : e (or M-x epa-dired-do-encrypt)
+ (select recipients by 'm' and click [OK])
+
+* MUA Integration
+
+The EasyPG Library can be used in combination with various MUA (Mail
+User Agents).
+
+** CVS version of Gnus
+
+CVS version of Gnus uses EasyPG by default. To make sure of that,
+check mml2015-use set to 'epg. Other options which affect on the
+EasyPG are
+
+ mml2015-signers
+ mml2015-encrypt-to-self
+ mml2015-cache-passphrase
+ mml2015-passphrase-cache-expiry
+ mml2015-verbose
+
+NOTE: You don't need pgg-epg.el in this case.
+
+** PGG based MUA
-* Security consideration
+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.
+
+Limitations of PGG
+
+- 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
+
+** SEMI based MUA
+
+SEMI is the MIME library used by Wanderlust, cmail, T-gnus, etc.
+
+There is an EasyPG capable SEMI library called EMIKO-EasyPG. It can
+be downloaded from the same site of the EasyPG distribution point.
+
+* Security
+
+There are security pitfalls around Emacs. EasyPG is written with
+avoiding them.
** Passphrase may leak to a temporary file.
-`call-process-region' writes data in region to a temporary file.
-The EasyPG Library does not use `call-process-region' to communicate with a gpg
-subprocess.
+The function call-process-region writes data in region to a temporary
+file. If your PGP library used this function, your passphrases would
+leak to the filesystem.
+
+The EasyPG Library does not use call-process-region to communicate
+with a gpg subprocess.
** Passphrase may be stolen from a core file.
If Emacs crashes and dumps core, Lisp strings in memory are also
-dumped within the core file. `read-passwd' function clears passphrase
-strings by `(fillarray string 0)'. However, Emacs performs compaction
-in gc_sweep phase. If GC happens before `fillarray', passphrase
-strings may be moved elsewhere in memory. Therefore, passphrase
-caching in elisp is generally a bad idea.
-
-The EasyPG Library dares to disable passphrase caching. Fortunately,
-there is more secure way to cache passphrases - use gpg-agent. Elisp
-programs can set `epg-context-passphrase-callback' to cache user's
-passphrases, it is not recommended though.
+dumped within the core file. read-passwd function clears passphrase
+strings by (fillarray string 0) to avoid this risk. However, Emacs
+performs compaction in gc_sweep phase. If GC happens before fillarray,
+passphrase strings may be moved elsewhere in memory. Therefore,
+passphrase caching in elisp is generally a bad idea.
+
+The EasyPG Library dares to disable passphrase caching. Fortunately,
+there is more secure way to cache passphrases - use gpg-agent.