all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Werner Koch <wk@gnupg.org>, Miles Bader <miles@gnu.org>,
	rms@gnu.org, Daiki Ueno <ueno@unixuser.org>,
	emacs-devel@gnu.org
Subject: Re: Fix needed for communication with gpg-agent
Date: Thu, 22 Feb 2007 23:00:49 +0100	[thread overview]
Message-ID: <m2d5417sz2.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <87slcynii0.fsf@stupidchicken.com> (Chong Yidong's message of "Thu\, 22 Feb 2007 13\:40\:23 -0500")

Chong Yidong <cyd@stupidchicken.com> wrote:

> Werner Koch <wk@gnupg.org> writes:
>
>>> Admittedly, it is a rather naughty solution: GPG is called through an
>>> elisp terminal (as implemented by `make-term' in term.el), with a
>>> modified process filter whose purpose is to send GPG the string to be
>>
>> With all that code running in emacs, I doubt that it makes sense at
>> all to use the curses versions of Pinentry.
>
> In that case, I think Emacs should disable use of gpg-agent when
> running in a console, except when gpg-agent already has a passphrase
> cached.  Then all we need is some method for Emacs to determine if the
> necessary passphrase is cached.

Even if it is possible to determine this (I don't know right now),
there is an additional problem:  the key caching of the gpg-agent
times out after an configurable interval, so after that time emacs
would suddenly stop using the agent -- this sounds like undesirable to
me... 

> If gpg-agent does not have the
> passphrase, Emacs will then prompting for the passphrase and send it
> to GPG, without caching it in Elisp (i.e. subsequent calls to GPG will
> require entering the passphrase again).

I think this suggestion is based on a misunderstanding -- the security
problems in the current implementation (when not using gpg-agent) has
nothing to do with caching, it comes form the fact, that emacs writes
the the passphrase to an temporary file (which is then feed to gpg).

>> Is it possible to enhance server-start/emacsclient so that it does not
>> edit a file but asks for string and returns that one?  Pinentry could
>> then use this feature for user interaction.
>
> I'm not sure how this suggestion could work.

I haven't fully understood this idea, too.  In general I doubt, that
it is an good idea to make gpg-agent depend on an running emacs for
passphrase input -- even if many emacs users are using emacs as there
primary working environment and therefor have it running all the
time -- not everyone does...

cheers
sascha
-- 
Sascha Wilde
Life's too short to read boring signatures

  reply	other threads:[~2007-02-22 22:00 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 20:57 Fix needed for communication with gpg-agent Richard Stallman
2007-02-18 17:42 ` Chong Yidong
2007-02-19 23:35   ` Miles Bader
2007-02-20  1:59     ` Chong Yidong
2007-02-22 17:31       ` Chong Yidong
2007-02-22 17:44         ` Chong Yidong
2007-02-22 18:04         ` Werner Koch
2007-02-22 18:40           ` Chong Yidong
2007-02-22 22:00             ` Sascha Wilde [this message]
2007-02-22 22:47               ` Chong Yidong
2007-02-23 20:01                 ` Sascha Wilde
2007-02-24  8:28                   ` Richard Stallman
2007-02-23 22:09               ` Richard Stallman
2007-02-23 23:41                 ` Sascha Wilde
2007-02-25  4:06                   ` Richard Stallman
2007-02-25 19:32                     ` Chong Yidong
2007-02-25 19:50                       ` Andreas Schwab
2007-02-25 20:22                         ` David Kastrup
2007-02-26  3:27                       ` Richard Stallman
2007-02-26 10:27                         ` Werner Koch
2007-02-27  7:38                           ` Richard Stallman
2007-02-27  8:53                             ` Werner Koch
2007-02-28  2:37                               ` Richard Stallman
2007-02-23  8:53             ` Werner Koch
2007-02-23 10:27               ` Sascha Wilde
2007-02-23 16:23               ` Chong Yidong
2007-02-23 16:47                 ` Werner Koch
2007-02-23 19:37                   ` Chong Yidong
2007-02-23 20:10                     ` Sascha Wilde
2007-02-23 22:10                     ` Richard Stallman
2007-02-23 22:09                   ` Richard Stallman
2007-02-23 23:03                     ` Chong Yidong
2007-02-23 17:13           ` Andreas Schwab
2007-02-23 18:30             ` Kim F. Storm
2007-02-23 18:07           ` Stefan Monnier
2007-02-24 14:08             ` Miles Bader
2007-02-23 19:35         ` Richard Stallman
2007-02-20 13:43     ` Richard Stallman
2007-02-20 15:35       ` Chong Yidong
2007-02-21  8:37         ` Richard Stallman
2007-02-21 12:04           ` Chong Yidong
2007-02-22 17:21             ` Richard Stallman
2007-02-20 15:11   ` Kim F. Storm
2007-02-20 15:45     ` Chong Yidong
2007-02-21  8:37     ` Richard Stallman
2007-02-21 13:11       ` Chong Yidong
2007-02-22  7:19         ` Richard Stallman
     [not found]   ` <E1HJCsN-000541-DO@fencepost.gnu.org>
2007-02-21 22:41     ` Sascha Wilde
2007-02-21 23:15       ` Kim F. Storm
2007-02-22  0:14         ` Chong Yidong
2007-02-22  8:04           ` Werner Koch
2007-02-22 12:09           ` Kim F. Storm
2007-02-22  8:13         ` Werner Koch
2007-02-23 10:22           ` Richard Stallman
2007-02-23 13:20             ` Werner Koch
2007-02-23 16:40               ` Chong Yidong
2007-02-23 22:09               ` Richard Stallman
2007-02-23 19:36           ` Richard Stallman
2007-02-23 23:25             ` Chong Yidong
2007-02-23 23:58               ` Kim F. Storm
2007-02-24  0:19                 ` Chong Yidong
2007-02-24  0:57                   ` Kim F. Storm
2007-02-24  9:58                     ` Sascha Wilde

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=m2d5417sz2.fsf@kenny.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=rms@gnu.org \
    --cc=ueno@unixuser.org \
    --cc=wk@gnupg.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.