From: Daiki Ueno <ueno@unixuser.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: "epa (Caching Passphrases)"
Date: Wed, 06 Oct 2010 22:25:48 +0900 [thread overview]
Message-ID: <8739sjmp0j.fsf@broken.deisui.org> (raw)
In-Reply-To: <87mxqrh4ah.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 06 Oct 2010 07:52:22 -0500")
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
Ted Zlatanov <tzz@lifelogs.com> writes:
>>> Unfortunately Gnus is distributed alone as well, so a info link would
>>> not work everywhere. Can you suggest a rewrite of that section in
>>> addition to the link to help people in that situation?
>
> DU> GnuPG is also distributed alone but we refer to its info node with:
> DU> @pxref{Top, , Top, gnupg, Using the GNU Privacy Guard}
> DU> from the Emacs manual, etc.
>
> DU> What's the problem?
>
> I explained the problem and said I'll put the link in. What I requested
> was a suggestion on rewording that section for those who don't have the
> EPA manual available.
Then how about this:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: auth-epa.diff --]
[-- Type: text/x-diff, Size: 2946 bytes --]
=== modified file 'doc/misc/auth.texi'
--- doc/misc/auth.texi 2010-09-02 00:55:51 +0000
+++ doc/misc/auth.texi 2010-10-06 13:17:50 +0000
@@ -59,6 +59,7 @@
* Help for users::
* Secret Service API::
* Help for developers::
+* GnuPG and EasyPG Assistant Configuration::
* Index::
* Function Index::
* Variable Index::
@@ -176,16 +177,8 @@
If you don't customize @code{auth-sources}, you'll have to live with
the defaults: any host and any port are looked up in the netrc
-file @code{~/.authinfo.gpg}. This is an encrypted file if and only if
-you set up EPA, which is strongly recommended.
-
-@lisp
-(require 'epa-file)
-(epa-file-enable)
-;;; VERY important if you want symmetric encryption
-;;; irrelevant if you don't
-(setq epa-file-cache-passphrase-for-symmetric-encryption t)
-@end lisp
+file @code{~/.authinfo.gpg}, which is a GnuPG encrypted file.
+@xref{GnuPG and EasyPG Assistant Configuration}.
The simplest working netrc line example is one without a port.
@@ -271,6 +264,54 @@
@end defun
+@node GnuPG and EasyPG Assistant Configuration
+@appendix GnuPG and EasyPG Assistant Configuration
+
+In Emacs 23 or later there is an option @code{auto-encryption-mode} to
+automatically decrypt @code{*.gpg} files and it is enabled by default
+so there is no setting is needed. If you are using earlier versions
+of Emacs for some reason, you will need:
+
+@lisp
+(require 'epa-file)
+(epa-file-enable)
+@end lisp
+
+If you want your GnuPG passwords to be cached, setup @code{gpg-agent}
+or EasyPG Assitant
+@pxref{Caching Passphrases, , Caching Passphrases, epa}
+
+For those who are using older vesions of Emacs, here are some portion
+copied from the EasyPG Assitant manual:
+
+Here are some questions:
+
+@enumerate
+@item Do you use GnuPG version 2 instead of GnuPG version 1?
+@item Do you use symmetric encryption rather than public key encryption?
+@item Do you want to use gpg-agent?
+@end enumerate
+
+Here are configurations depending on your answers:
+
+@multitable {111} {222} {333} {configuration configuration configuration}
+@item @b{1} @tab @b{2} @tab @b{3} @tab Configuration
+@item Yes @tab Yes @tab Yes @tab Nothing to do.
+@item Yes @tab Yes @tab No @tab You can't, without gpg-agent.
+@item Yes @tab No @tab Yes @tab Nothing to do.
+@item Yes @tab No @tab No @tab You can't, without gpg-agent.
+@item No @tab Yes @tab Yes @tab Set up elisp passphrase cache.
+@item No @tab Yes @tab No @tab Set up elisp passphrase cache.
+@item No @tab No @tab Yes @tab Nothing to do.
+@item No @tab No @tab No @tab You can't, without gpg-agent.
+@end multitable
+
+To setup gpg-agent, follow the instruction in GnuPG manual.
+@pxref{Invoking GPG-AGENT, , Invoking GPG-AGENT, gnupg}.
+
+To set up elisp passphrase cache, set
+@code{epa-file-cache-passphrase-for-symmetric-encryption}.
+
@node Index
@chapter Index
@printindex cp
[-- Attachment #3: Type: text/plain, Size: 15 bytes --]
--
Daiki Ueno
next prev parent reply other threads:[~2010-10-06 13:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 0:09 auth-sources: 8 password prompts for accessing one single imap server Tassilo Horn
2010-09-27 6:38 ` Vegard Vesterheim
2010-09-27 7:59 ` Drew Hess
2011-02-25 22:19 ` Ted Zlatanov
2010-09-27 16:49 ` Lars Magne Ingebrigtsen
2010-09-27 17:13 ` Vegard Vesterheim
2010-09-27 17:21 ` Lars Magne Ingebrigtsen
2010-09-27 20:50 ` Tassilo Horn
2010-09-27 20:57 ` Lars Magne Ingebrigtsen
2010-09-30 6:30 ` Tassilo Horn
2010-09-30 15:44 ` Ted Zlatanov
2010-10-05 7:16 ` Tassilo Horn
2010-10-06 7:20 ` "epa (Caching Passphrases)" Daiki Ueno
2010-10-06 12:22 ` Ted Zlatanov
2010-10-06 12:38 ` Daiki Ueno
2010-10-06 12:52 ` Ted Zlatanov
2010-10-06 13:25 ` Daiki Ueno [this message]
2010-10-07 19:38 ` Lars Magne Ingebrigtsen
2010-10-08 15:38 ` Ted Zlatanov
2010-09-27 21:01 ` auth-sources: 8 password prompts for accessing one single imap server Ted Zlatanov
2010-09-27 21:42 ` Tassilo Horn
2010-09-28 7:25 ` Gijs Hillenius
2010-09-28 10:19 ` Lars Magne Ingebrigtsen
2010-09-28 10:32 ` Gijs Hillenius
2010-09-28 12:04 ` Dave Goldberg
2010-09-28 13:10 ` Gijs Hillenius
2010-09-28 13:42 ` Gijs Hillenius
2010-09-27 16:54 ` Lars Magne Ingebrigtsen
2010-09-27 18:37 ` Ted Zlatanov
2010-09-27 18:48 ` Lars Magne Ingebrigtsen
2010-09-27 18:52 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739sjmp0j.fsf@broken.deisui.org \
--to=ueno@unixuser.org \
--cc=ding@gnus.org \
--cc=tzz@lifelogs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).