From: "Jochen Küpper" <jochen-+It19tn3Rl9sbm7dSapR3bNAH6kLmebB@public.gmane.org>
Subject: Re: Signing issues with gnus from CVS
Date: Thu, 18 May 2006 15:21:41 +0200 [thread overview]
Message-ID: <9e3bf7a2oq.fsf@gowron.rz-berlin.mpg.de> (raw)
In-Reply-To: <87ejyrfqsm.fsf-iS72tiDCHhS1g9c2/K602IXGvZO2VSpW@public.gmane.org> (Bastien's message of "Thu, 18 May 2006 14:42:01 +0200")
Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
> Same here. The only clue is this: you're not alone. gnupg complains
> about wrong password (sent by pgg?). This happend with gnus cvs of
> this morning as well.
Oh, I see... I had a probably related /two or three/ times over the
last week: When sending a signed copy Gnus complains about a wrong
passphrase, but actually had correctly send the message. Signing the
Gcc for IMAP storage didn't work, however.
Undo till the "Gcc:" was back, C-c C-c again, saying no to
resend-question did ask me for the passphrase again and worked.
Maybe something with passphrase caching?
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
(Part 3 you find in my messages before fall 2003.)
next prev parent reply other threads:[~2006-05-18 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 23:07 Norman Walsh
[not found] ` <smuzmhfr0zb.fsf@linuxpal.mit.edu>
2006-05-18 12:30 ` Norman Walsh
2006-05-18 12:42 ` Bastien
[not found] ` <87ejyrfqsm.fsf-iS72tiDCHhS1g9c2/K602IXGvZO2VSpW@public.gmane.org>
2006-05-18 13:21 ` Jochen Küpper [this message]
2006-05-19 22:56 ` PGG broken? (was: Signing issues with gnus from CVS) Marcus Frings
2006-05-23 21:25 ` PGG broken? Marcus Frings
2006-05-24 16:10 ` Norman Walsh
2006-06-02 3:44 ` Andreas Seltenreich
2006-06-04 4:38 ` Andreas Seltenreich
2006-06-18 15:09 ` Marcus Frings
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=9e3bf7a2oq.fsf@gowron.rz-berlin.mpg.de \
--to=jochen-+it19tn3rl9sbm7dsapr3bnah6klmebb@public.gmane.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).