X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=README;h=d56f6df0e48b41477654e0f17f1f3d28a7b54ce2;hb=9959124798b862332baed742cf607e495144a583;hp=c370ac87003b607c1d56a6f7ad97f73f012a892d;hpb=afe1a4421ada9e44c87787257aad124648973e11;p=elisp%2Fepg.git

diff --git a/README b/README
index c370ac8..d56f6df 100644
--- a/README
+++ b/README
@@ -22,25 +22,32 @@ library to interact with GnuPG.
 
 * Advantages over other competitors
 
+There are many competitors of EasyPG such as Mailcrypt, PGG, gpg.el,
+etc.  EasyPG has some advantages over them.
+
 ** EasyPG avoides potential security flaws of Emacs.
 
-*** `call-process-region' writes data in region to a temporary file.
+*** `call-process-region' writes data in region to temporary files.
 
-PGG and gpg.el use `call-process-region' to communicate with a gpg
-subprocess.  Your passphrases may leak to the filesystem.
+`call-process-region' writes data in region to temporary files.  PGG
+and gpg.el use `call-process-region' to communicate with a gpg
+subprocess.  Your passphrases leak to the filesystem!
 
 *** There is no way to clear strings safely.
 
 If Emacs crashed and dumps core, passphrase strings in memory are also
-dumped with the core file.  `read-passwd' function clears passphrase
-strings by `(fillarray string 0)'.  However, it is not perfect.  Emacs
-does compaction of small strings in gc_sweep phase.  If GC happens
-before `fillarray', passphrase strings may be copied elsewhere in
-memory.  So, it is recommended that if you are done with passphrase
-you should clear it manually.  However, PGG and gpg.el enables
-passphrase caching by default.
-
-** Most GnuPG features are accessible from Emacs
-
-As the name indicates, EasyPG is inspired by GPGME (GnuPG Made Easy),
-and the library interface is close to GPGME.
+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.  It is recommended that as
+soon as you are done with passphrase you should clear it manually.
+However, PGG and gpg.el can keep passphrase strings in cache for a
+while and this behavior is their default!
+
+** GnuPG features are directly accessible from Emacs
+
+Other competitors provide only specific features of GnuPG since they
+still support PGP 2.*, 5.*, 6.*.  As the name indicates, EasyPG is
+inspired by GPGME (GnuPG Made Easy), and the library interface is
+close to GPGME.  With EasyPG you can benefit from a lot of features of
+GnuPG.