Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: pgg doesn't mention that the signature is untrusted
Date: Fri, 11 Oct 2002 06:17:41 +0200	[thread overview]
Message-ID: <iluy99538yi.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87it09ep8f.fsf@mail.paradoxical.net> (Josh Huber's message of "Thu, 10 Oct 2002 21:30:40 -0400")

Josh Huber <huber@alum.wpi.edu> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> Not here, it seems to be a bug; PGG stores the passphrase on the key
>> ID actually used by GnuPG to sign something, but it later looks up
>> the passphrase using the first private key ID from
>> --list-secret-keys.  This didn't work for me as I have many secret
>> keys.  Hm.  Shouldn't be difficult to fix, I think.
>
> Perhaps it works for me because of this configuration?
>
> (setq jmh::primary-key "6B21489A")
> (setq pgg-passphrase-cache-expiry 300)
> (setq pgg-default-user-id jmh::primary-key)

Yes, I leave the `pgg-default-user-id' to its default value "jas",
which matches several keys and PGG picks the first one which turns out
to be a expired key I don't use anymore.  PGG should handle this
without additional configuration IMHO.  I added it to my TODO list..




  reply	other threads:[~2002-10-11  4:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 12:50 David Kågedal
2002-10-10 15:08 ` Simon Josefsson
2002-10-10 15:23   ` Josh Huber
2002-10-10 15:47     ` Simon Josefsson
2002-10-10 16:31   ` David Kågedal
2002-10-10 16:41     ` Simon Josefsson
2002-10-10 17:14       ` David Kågedal
2002-10-10 18:44       ` Mark Trettin
2002-10-10 20:21         ` Simon Josefsson
2002-10-11  0:39           ` Josh Huber
2002-10-11  1:08             ` Simon Josefsson
2002-10-11  1:30               ` Josh Huber
2002-10-11  4:17                 ` Simon Josefsson [this message]
2002-10-17 10:57                   ` Mark Trettin

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=iluy99538yi.fsf@latte.josefsson.org \
    --to=jas@extundo.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).