From: Daniel Mendler <mail@daniel-mendler.de>
To: 61277@debbugs.gnu.org
Cc: yantar92@posteo.net, stefan@marxist.se, monnier@iro.umontreal.ca
Subject: bug#61277: FR: ELPA security - Restrict package builds to signed git commits
Date: Sat, 04 Feb 2023 19:19:06 +0100 [thread overview]
Message-ID: <87pmapqoo5.fsf@daniel-mendler.de> (raw)
As discussed on emacs-devel it would be good if ELPA security could be
improved, preventing potential breaches on the side of the source
repository. This feature becomes more relevant the more packages are
:auto-sync'ed from their source repository.
My git commits are usually signed, so one could check the signature of
each commit which leads to a package build. This feature could be opt-in
for now, enabled via an attribute :signature in the elpa-packages
configuration. Maybe elpa-packages could store the fingerprint(s) of the
expected GPG key(s)?
In the case of a breach, both the SSH and GPG keys may be stolen, which
would allow an attacker to create commits on hosted repositories, such
that the mechanism would not help. However the source repository may
also get compromised via other vectors.
https://lists.gnu.org/archive/html/emacs-devel/2023-02/msg00120.html
next reply other threads:[~2023-02-04 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 18:19 Daniel Mendler [this message]
2023-02-05 11:19 ` bug#61277: FR: ELPA security - Restrict package builds to signed git commits Ihor Radchenko
2023-02-07 3:56 ` Richard Stallman
2023-02-07 11:44 ` Ihor Radchenko
2023-02-07 12:40 ` Eli Zaretskii
2023-02-09 4:28 ` Richard Stallman
2023-02-09 12:07 ` Ihor Radchenko
2023-02-12 4:04 ` Richard Stallman
2023-02-07 12:10 ` Eli Zaretskii
2023-02-12 6:37 ` Stefan Kangas
2023-02-12 10:32 ` Daniel Mendler
2023-02-15 5:17 ` Richard Stallman
2023-02-15 5:17 ` Richard Stallman
2023-02-15 13:37 ` Stefan Kangas
2023-02-15 16:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-26 2:59 ` Richard Stallman
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=87pmapqoo5.fsf@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--cc=61277@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
--cc=yantar92@posteo.net \
/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).