From: Lars Ingebrigtsen <larsi@gnus.org>
To: Amin Bandali <bandali@gnu.org>
Cc: 37528@debbugs.gnu.org
Subject: bug#37528: 27.0.50; Can't view gpg-signed messages in Gnus anymore
Date: Fri, 27 Sep 2019 01:45:53 +0200 [thread overview]
Message-ID: <87pnjmei4u.fsf@gnus.org> (raw)
In-Reply-To: <87r242hlad.fsf@gnu.org> (Amin Bandali's message of "Thu, 26 Sep 2019 16:09:30 -0400")
Amin Bandali <bandali@gnu.org> writes:
> I’ve noticed, after pulling from trunk today, that I’m no longer able to
> read GPG-signed messages sent by authors whose key I don’t have in my
> keyring. This is what I see in the article buffer for such messages
> now:
>
> [[PGP Signed Part:No public key for DF338F09980791EF created at 2019-09-26T09:45:48-0400 using RSA]]
> Error! Result from decryption:
>
> No public key for DF338F09980791EF created at 2019-09-26T09:45:48-0400 using RSA
>
> [[End of PGP Signed Part]]
This is a bug I introduced yesterday, but I can't quite see how it's
happening now -- this code path should now only be if
(if (or (not info)
(equal info "")
(equal subtype "encrypted")
that is, it shouldn't be possible to happen for /signed parts, just for
/encrypted parts.
Are you completely up-to-date on the master branch?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-09-26 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 20:09 bug#37528: 27.0.50; Can't view gpg-signed messages in Gnus anymore Amin Bandali
2019-09-26 23:45 ` Lars Ingebrigtsen [this message]
2019-09-27 2:38 ` Amin Bandali
2019-09-27 14:31 ` Lars Ingebrigtsen
2019-09-27 15:53 ` Amin Bandali
2019-10-21 20:56 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnjmei4u.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37528@debbugs.gnu.org \
--cc=bandali@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).