Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jens Lechtenboerger <lechtej@uni-muenster.de>
Subject: Re: GPG decryption with ngnus?
Date: Fri, 12 May 2006 17:22:42 +0200	[thread overview]
Message-ID: <m23bffclod.fsf@pcwi4002.uni-muenster.de> (raw)
In-Reply-To: <m3y7xn1gwf.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Jens Lechtenboerger <lechtej@uni-muenster.de> writes:
>
>> When reading encrypted e-mail, I get asked "Decrypt (PGP) part?"
>> After pressing "y" and entering my passphrase, the *Article* buffer
>> contains just header lines, but nothing else (no body, no
>> plaintext).
>
> I think this may have just been fixed in CVS Gnus.

No.  This is what happened: In my gpg.conf "use-agent" was enabled,
but there was no agent.  So, gpg issues a warning that there is no
Agent, decrypts and verifies everything just fine, and exits with
status 2.  Then, pgg assumes a failure (although the *pgg-gpg-debug*
buffer contains success messages).

I've got a different problem now.  Sometimes I can't decrypt mail
because pgg claims that my passphrase is incorrect.  The
*pgg-gpg-debug* buffer also has corresponding error messages.  I'm
pretty sure that I type in my passphrase correctly, though.  The
prompt appears over and over again, and I'm having difficulties
escaping it.  C-g doesn't help.  (I'm typing an Umlaut then, which
leads to "error in process filter: Attempt to change byte length of
a string" and allows me to escape.  Once, I even crashed Emacs with
repeated Umlauts and C-g's...  Is there a better escape sequence?)
So for this only occurs with large (> 5.7 MB) encrypted attachments.
Manual decryption with gpg works just fine.

Any ideas?

Jens

      reply	other threads:[~2006-05-12 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  9:00 Jens Lechtenboerger
2006-04-30 10:45 ` Lars Magne Ingebrigtsen
2006-05-12 15:22   ` Jens Lechtenboerger [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=m23bffclod.fsf@pcwi4002.uni-muenster.de \
    --to=lechtej@uni-muenster.de \
    /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).