Re: mutt/1025: mutt: GPG/PGP Passphrase stored even when wrong
On Mon, Aug 01, 2005 at 07:25:02PM -0700, Brendan Cully wrote:
> On Monday, 01 August 2005 at 19:02, Will Yardley wrote:
> > On Mon, Aug 01, 2005 at 02:43:00PM -0700, Brendan Cully wrote:
> > > > > > Synopsis: mutt: GPG/PGP Passphrase stored even when wrong
> > > Sorry for the bad gnats message. It IS fixed now.
> > if I type in the wrong passphrase, I get:
> > gpg: /tmp/mutt-mitch-1228-20983-14: sign+encrypt failed: bad passphrase
> >
> > each time I try to send the message... in other words, the passphrase
> > doesn't appear to be forgotten if I type it wrong.
> Whoops, I forgot to do the encrypt bits. Should be fixed now.
Yup - seems good now.
Also (sorry for the thread hijack), if I type a bad passphrase (on the
receiving end) when decoding a signed / encrypted inline message, I see:
[-- PGP output follows (current time: Mon Aug 1 19:37:39 2005) --]
gpg: decryption failed: secret key not available
[-- End of PGP output --]
but at the bottom:
PGP signature successfully verified.
(yes, the signature is verified, but the message couldn't be decrypted)
or, with pgp-mime:
[-- PGP output follows (current time: Mon Aug 1 19:40:04 2005) --]
gpg: decryption failed: secret key not available
[-- End of PGP output --]
Could not decrypt PGP message
I don't know if it's too hard for mutt to figure out when the passphrase
is wrong with the current architecture, but maybe there's a way to make
it work a little better?
w