From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: pgg-encrypt is a pain in the neck Date: Tue, 02 Jan 2007 11:37:38 -0500 Message-ID: References: <6662a3b9-1148-4aa0-bd2d-29a67be38d76@well-done.deisui.org> <5a520e06-4ee3-4c4f-9345-d49a666516f9@well-done.deisui.org> <7f60c21d-2f66-4c4b-9abb-e377ca24a153@well-done.deisui.org> <844cd50a-ec18-4b09-a057-35bdfb5173fd@well-done.deisui.org> <8ba25607-9381-4a27-ae53-8b0f3ccc3ac1@well-done.deisui.org> <366fa6ab-42a0-4df5-a17f-4ac3d1744d78@well-done.deisui.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1167755909 20509 80.91.229.12 (2 Jan 2007 16:38:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 2 Jan 2007 16:38:29 +0000 (UTC) Cc: wilde@sha-bang.de, emacs-devel@gnu.org, reinersteib+gmane@imap.cc Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 02 17:38:26 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1H1meV-0006Z8-Ct for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2007 17:38:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1meU-00006N-PN for ged-emacs-devel@m.gmane.org; Tue, 02 Jan 2007 11:38:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H1meF-0008Va-Vm for emacs-devel@gnu.org; Tue, 02 Jan 2007 11:38:00 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H1meE-0008UH-Sc for emacs-devel@gnu.org; Tue, 02 Jan 2007 11:37:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H1meE-0008U3-LV for emacs-devel@gnu.org; Tue, 02 Jan 2007 11:37:58 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1meE-0004uW-6K for emacs-devel@gnu.org; Tue, 02 Jan 2007 11:37:58 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1H1mdu-00070b-95; Tue, 02 Jan 2007 11:37:38 -0500 Original-To: Daiki Ueno In-reply-to: (message from Daiki Ueno on Tue, 02 Jan 2007 09:28:42 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:64640 Archived-At: Do you mean "the gpg agent directions" is one I wrote? You asked me to write a documentation of gpg-agent usage for the Emacs Manual, and I sent the following to you privately. Yes, that is the text I mean. Would someone please install this in the Message mode manual? Some Emacs commands internally call GnuPG (the @command{gpg} command) to perform data encryption, and in certain cases (decrypting or signing for example), @command{gpg} requires user's passphrase. Currently the recommended way to supply your passphrase to @command{gpg} is to use the @command{gpg-agent} program. To use @command{gpg-agent} in Emacs, you need to run the following command from the shell before starting Emacs. @example eval `gpg-agent --daemon` @end example This will invoke @command{gpg-agent} and set the environment variable @code{GPG_AGENT_INFO} to allow @command{gpg} to communicate with it. It might be good idea to put this command in your @file{.xsession} or @file{.bash_profile}. @xref{Invoking GPG-AGENT, , , gnupg, Using the GNU Privacy Guard}. Once your @command{gpg-agent} is set up, it will ask you for a passphrase as needed for @command{gpg}. Under the X Window System, you will see a new passphrase input dialog appear. The dialog is provided by PIN Entry (the @command{pinentry} command), and as of version 0.7.2, @command{pinentry} cannot cooperate with Emacs on a single tty. So, if you are using a text console, you may need to put a passphrase into gpg-agent's cache beforehand. The following command does the trick. @example gpg --use-agent --sign < /dev/null > /dev/null @end example The Lisp variable @code{pgg-gpg-use-agent} controls whether to use @command{gpg-agent}. See also @xref{Caching passphrase, , , pgg, The PGG Manual}.