From: "Michael Teichgräber" <mt@wmipf.in-berlin.de>
Cc: ding@gnus.org
Subject: Re: pgg passphrase caching
Date: Mon, 28 Apr 2003 01:26:38 +0200 [thread overview]
Message-ID: <87wuhfed3l.fsf@wmipf.in-berlin.de> (raw)
In-Reply-To: <86fzo3g2v7.fsf@jochen.rijnh.nl> (Jochen =?iso-8859-1?q?K=FCpper's?= message of "Sun, 27 Apr 2003 21:24:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Jochen Küpper <jochen@jochen-kuepper.de> writes:
> Just updated to cvs HEAD. Now pgg passphrase caching doesn't work any
> more:( Used to work with OGnus-0.18. [1] (Using Emacs-21.2.1 on Cygwin).
Does this happen on signing only, i.e. if you have entered your
passphrase to sign a mail, and on subsequent signings the cache turns
out not to work, or is decryption envolved too?
The first case, passphrase caching for subsequent signings, works for
me.
> [1] I have tested it with cvs o0-18 (works) and o0-19 (doesn't work).
If it is passphrase caching for (mainly) decryption, that does not
work, did you verify this on the same message?
There still is the behaviour described in Message
"pgg-decrypt-region: wrong key-ID displayed"
<87he9ww7pt.fsf@iridium.renata.de>, news.gnus.org:gnus.gnus-bug
that has a side-effect on decrypting mails, which have the sender's
key ID -- not the receipient's -- in the first PGP packet: In this
case pgg-decrypt-region will ask the passphrase cache (that already
contains the passphrase with my secret key ID) for the wrong (the
sender's) key ID.
--
Michael
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2003-04-27 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 19:24 Jochen Küpper
2003-04-27 20:36 ` Simon Josefsson
2003-04-28 23:21 ` Jochen Küpper
2003-04-29 0:45 ` Simon Josefsson
2003-04-29 7:50 ` Jochen Küpper
2003-04-27 23:26 ` Michael Teichgräber [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=87wuhfed3l.fsf@wmipf.in-berlin.de \
--to=mt@wmipf.in-berlin.de \
--cc=ding@gnus.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.
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).