<<< Date Index >>>     <<< Thread Index >>>

Re: 1.5.10 pgp handling broken



Paul Walker writes:
> On Tue, Aug 23, 2005 at 09:39:13AM +0100, Lars Hecking wrote:
> 
> >  process and got dumped straight into the pager. Under 1.5.10, I get only
> >  a warning message "Could not copy message"; I effectively cannot read
> >  this particular message quickly, I have to wait around 80s (gpg timeout)
> 
> So you get that message while it's blocked waiting for gpg to finish...? Or
> did I misunderstand?
 
 I get that message when I'm trying to ^C out of gpg, while mutt shows the
 "Invoking PGP..." message.

 One further piece of information: this only happens for old-style pgp
 signatures. It works just fine for PGP/MIME. This is how gpg is involved
 for PGP/MIME:

$ ps -ef | grep gpg
user       4145  4059  5 11:24 pts/8    00:00:00 /usr/bin/gpg --status-fd=2 
--no-verbose --quiet --batch --output - --verify 
/tmp/mutt-hell-14728-4059-9.asc /tmp/mutt-hell-14728-4059-9

 and this for old style signatures:

$ ps -ef |grep gpg
user       4242  4059  4 11:25 pts/8    00:00:00 /usr/bin/gpg --charset utf-8 
--status-fd=2 --no-verbose --quiet --batch --output - 
/tmp/mutt-hell-14728-4059-13

 Just now I realised that my gpg.rc was quite old (v1.7), so I updated it
 to the latest (v3.4) from cvs, but it makes no difference.