unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Iakov Davydov <dav02.davs@myths.ru>
Cc: 28780@debbugs.gnu.org
Subject: bug#28780: 25.3; Bad signature from GNU ELPA whe coding-system-for-read is utf-8
Date: Tue, 10 Oct 2017 19:46:57 +0300	[thread overview]
Message-ID: <83sherosqm.fsf@gnu.org> (raw)
In-Reply-To: <CA+xYm8-XUAcw-o2T8fG8Ym+5cjU1MM9Q4hsMu0C9cpD8abDzLg@mail.gmail.com> (message from Iakov Davydov on Tue, 10 Oct 2017 16:09:57 +0000)

> From: Iakov Davydov <dav02.davs@myths.ru>
> Date: Tue, 10 Oct 2017 16:09:57 +0000
> 
> When installing a package (e.g. auctex), an error message appears:
> Failed to verify signature auctex-11.91.0.tar.sig:
> Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent <elpasign@elpa.gnu.org>
> Command output:
> gpg: [don't know]: indeterminate length for invalid packet type 14
> gpg: Signature made Tue 25 Jul 2017 11:10:02 PM CEST using DSA key ID 7FBDEF9B
> gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>" [unknown]
> 
> This only happens if the following line in my .emacs:
> (setq-default coding-system-for-read 'utf-8)
> 
> Steps to reproduce:
> 
> 1. Run emacs -Q
> 2. Execute `(setq-default coding-system-for-read 'utf-8)` (e.g. go to
> scratch, type this command, type C-x C-e).
> 3. M-x package-install auctex
> 4. Error message appears.
> 
> If step #2 is skipped, installation happens without an error.

Why do you need to do step 2?  You shouldn't do that, especially when
using commands that read binary files.  coding-system-for-read is for
temporarily forcing specific decoding of specific text, and should
otherwise be left alone.  And you definitely shouldn't change its
default value.

IOW, this sounds like a clear cockpit error.  Am I missing something?

> In fact, this or similar problem seems to be quite common, but often
> cannot be reproduced.
> 1. emacs bug#22971
> 2. https://emacs.stackexchange.com/questions/10046
> 3. https://github.com/jacksonrayhamilton/tern-context-coloring/issues/4
> 4. https://github.com/ananthakumaran/tide/issues/51
> 5. https://github.com/syl20bnr/spacemacs/issues/3669
> 6. https://www.reddit.com/r/emacs/comments/6t21lb/
> 7. https://www.linux.org.ru/forum/security/13718006 (In Russian)

I see no clear evidence that these reports are due to setting
coding-system-for-read.





  reply	other threads:[~2017-10-10 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 16:09 bug#28780: 25.3; Bad signature from GNU ELPA whe coding-system-for-read is utf-8 Iakov Davydov
2017-10-10 16:46 ` Eli Zaretskii [this message]
2017-10-10 18:55   ` Iakov Davydov
2017-10-10 19:26     ` Eli Zaretskii

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=83sherosqm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28780@debbugs.gnu.org \
    --cc=dav02.davs@myths.ru \
    /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).