From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Cc: Samuel Wales <samologist@gmail.com>
Subject: Re: is melpa just unsigned?
Date: Fri, 19 May 2023 02:02:59 +0200 [thread overview]
Message-ID: <87sfbtkx1o.fsf@web.de> (raw)
In-Reply-To: CAJcAo8u5LWaLsgMNM-gPuhmRGTD+GYs3-=N-J0WypO5kbjqYiA@mail.gmail.com
Samuel Wales <samologist@gmail.com> writes:
> as a debian user, i am used to all packages AND the package list being
> signed [i think]. i do not know all the security implications of not
> signing an archive list, but it sounds dodgy. in any case, the error
> should definitely not be there?
>
> if the archive contents file is not signed, what does htis mean in
> practice? what are the attack vectors?
If you get no answers here... since Melpa is not part of Emacs, maybe you
have more luck if you ask the Melpa people?
Michael.
next prev parent reply other threads:[~2023-05-19 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 4:21 is melpa just unsigned? Samuel Wales
2023-05-19 0:02 ` Michael Heerdegen [this message]
2023-05-20 19:00 ` Emanuel Berg
2023-05-21 23:36 ` Michael Heerdegen
2023-05-23 2:53 ` Samuel Wales
2023-05-23 3:17 ` Platon Pronko
2023-05-23 3:21 ` [External] : " Drew Adams
2023-05-23 17:47 ` Daniel Fleischer
2023-05-26 6:07 ` Samuel Wales
2023-05-29 13:12 ` Björn Bidar
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=87sfbtkx1o.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=samologist@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).