unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Daiki Ueno <ueno@gnu.org>
Cc: Werner Koch <wk@gnupg.org>, Ivan Shmakov <ivan@siamics.net>,
	19960@debbugs.gnu.org
Subject: bug#19960: epg: allow passing --keyring values via new epg-context-keyrings
Date: Tue, 21 Apr 2015 07:37:24 -0400	[thread overview]
Message-ID: <877ft5lnkb.fsf@lifelogs.com> (raw)
In-Reply-To: <87tww9rasv.fsf-ueno@gnu.org> (Daiki Ueno's message of "Tue, 21 Apr 2015 20:16:32 +0900")

On Tue, 21 Apr 2015 20:16:32 +0900 Daiki Ueno <ueno@gnu.org> wrote: 

DU> Werner Koch <wk@gnupg.org> writes:
>> Using a different keyring may result in some surprising behaviour and
>> thus I consider it is better to use use a different GNUPGHOME for a
>> different configuration.

DU> Thanks, I was expecting so.  Considering that, I'd suggest to make the
DU> patch less generic.  That is, assuming that the main use-case of an
DU> external keyring is signature verification, add an optional argument
DU> KEYRING to epg-verify-*, instead of extending epg-context.

I actively use GnuPG with two separate keyrings for file encryption and
decryption, that's why I thought this was useful. I'd like to keep both
keyrings in one place instead of overriding GPGHOME. But I don't feel
strongly about it and can adapt, if there are downsides I wasn't aware
existed.

Thanks!
Ted





      reply	other threads:[~2015-04-21 11:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 16:12 bug#19960: epg: allow passing --keyring values via new epg-context-keyrings Ivan Shmakov
2015-04-20 22:25 ` Ted Zlatanov
2015-04-21  1:40   ` Daiki Ueno
2015-04-21 10:04     ` Werner Koch
2015-04-21 11:16       ` Daiki Ueno
2015-04-21 11:37         ` Ted Zlatanov [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877ft5lnkb.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=19960@debbugs.gnu.org \
    --cc=ivan@siamics.net \
    --cc=ueno@gnu.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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).