all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r105466: epa-mail.el handles GnuPG groups.
Date: Wed, 17 Aug 2011 14:09:12 +0900	[thread overview]
Message-ID: <m3sjp062vb.fsf-ueno@unixuser.org> (raw)
In-Reply-To: <E1QtY6G-0002qa-Py@fencepost.gnu.org> (Richard Stallman's message of "Wed, 17 Aug 2011 00:51:32 -0400")

Richard Stallman <rms@gnu.org> writes:

>     epa has a nice feature to select keys interactively, which is based on
>     (group-expanded) key information in elisp level.  Try:
>
>     C-u M-x epa-mail-encrypt
>
>     and you will see the list of keys which will be used to encrypt, before
>     doing actual encryption.  This is useful for careful users who don't
>     want to encrypt emails with untrusted/unwanted keys.
>
> I have nothing against it; but when C-u is not used, why check the keys?
> Why not just pass the specified recipients to GPG and let it check them?

It could be possible but it does not help simplifying the code.  Now the
behavior is identical to what GPG does and I see no reason to add a
special case when C-u is not used.

> I think we are talking about different code.  I was talking about
> the code to check the keys.  I thought all that could be deleted
> by making epa not check the keys.
>
> However, if that code is needed for the C-u case, then it could not be
> deleted.

Yes, it is needed for the C-u case and also for encrypting files (not
emails), importing/exporting keys, etc.

Regards,
-- 
Daiki Ueno



      reply	other threads:[~2011-08-17  5:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1QtB5W-00016k-0J@vcs.savannah.gnu.org>
     [not found] ` <m339h1x074.fsf-ueno@unixuser.org>
     [not found]   ` <E1QtTBx-0000ye-Lt@fencepost.gnu.org>
2011-08-17  1:32     ` /srv/bzr/emacs/trunk r105466: epa-mail.el handles GnuPG groups Daiki Ueno
2011-08-17  4:51       ` Richard Stallman
2011-08-17  5:09         ` Daiki Ueno [this message]

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=m3sjp062vb.fsf-ueno@unixuser.org \
    --to=ueno@unixuser.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.