From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: is melpa just unsigned?
Date: Sat, 20 May 2023 21:00:10 +0200 [thread overview]
Message-ID: <871qjaeslh.fsf@dataswamp.org> (raw)
In-Reply-To: 87sfbtkx1o.fsf@web.de
>> as a debian user, i am used to all packages AND the package
>> list being signed [i think].
Here are some 733 lines to read how they do it for Debian:
https://www.debian.org/doc/manuals/securing-debian-manual/deb-pack-sign.en.html
>> what are the attack vectors?
Malicious code inserted into the software supply chain *ka-boom*
> If you get no answers here... since Melpa is not part of
> Emacs, maybe you have more luck if you ask the Melpa people?
You mean they don't read here? :(
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-05-20 19:00 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
2023-05-20 19:00 ` Emanuel Berg [this message]
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=871qjaeslh.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
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).