From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 33825@debbugs.gnu.org, clemera <clemens.radermacher@posteo.de>
Subject: bug#33825: 25.2; , Failing to verify signature for ELPA debbugs package
Date: Mon, 16 Sep 2019 15:28:07 +0200 [thread overview]
Message-ID: <m2k1a85q1k.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=-rUT=YijPQt7rZm5OeZLQ-bkfh7W2dnhhj8YHO_C=Cw@mail.gmail.com> (Stefan Kangas's message of "Mon, 16 Sep 2019 13:04:55 +0200")
>>>>> On Mon, 16 Sep 2019 13:04:55 +0200, Stefan Kangas <stefan@marxist.se> said:
Stefan> Robert Pluim <rpluim@gmail.com> writes:
Stefan> The reporter verified he was indeed using http. Is there anything
Stefan> that can or should be done here, or is this to be closed as notabug?
>>
>> I think this is notabug. We can always reopen it if needed.
Stefan> Perhaps we could also add something about this issue to PROBLEMS?
Maybe.
Stefan> How about also adding a recommendation to use https, as far as
Stefan> possible, for package archives? I guess that could be added to both
Stefan> the doc string of package-archives and possibly also the manual. That
Stefan> would help security and avoid issues such as these.
This Iʼd be more in favour of.
Robert
next prev parent reply other threads:[~2019-09-16 13:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 13:38 bug#33825: 25.2; Failing to verify signature for ELPA debbugs package clemera
2018-12-21 23:39 ` Glenn Morris
2018-12-22 12:08 ` bug#33825: 25.2; , " clemera
2018-12-30 12:12 ` Robert Pluim
2018-12-30 12:34 ` Clemens Radermacher
2018-12-30 12:55 ` Robert Pluim
2019-09-13 19:50 ` Stefan Kangas
2019-09-16 9:07 ` Robert Pluim
2019-09-16 11:04 ` Stefan Kangas
2019-09-16 13:28 ` Robert Pluim [this message]
2019-09-16 14:29 ` Eli Zaretskii
2019-09-16 19:13 ` Stefan Kangas
2019-09-17 13:34 ` Robert Pluim
2019-09-20 17:24 ` Stefan Kangas
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=m2k1a85q1k.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=33825@debbugs.gnu.org \
--cc=clemens.radermacher@posteo.de \
--cc=stefan@marxist.se \
/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).