From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: mail@daniel-mendler.de, 61277@debbugs.gnu.org,
yantar92@posteo.net, monnier@iro.umontreal.ca
Subject: bug#61277: FR: ELPA security - Restrict package builds to signed git commits
Date: Sat, 25 Feb 2023 21:59:45 -0500 [thread overview]
Message-ID: <E1pW7GL-0007zb-WE@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmn1q23w1XT94vHXU5jsrnZeiHs0RV+O1b4GYySiDKNQwg@mail.gmail.com> (message from Stefan Kangas on Wed, 15 Feb 2023 05:37:36 -0800)
Please forgive my delay in replying.
> If an attacker can introduce a commit containing malicious code, and
> create a new git tag pointing to that commit, the GNU ELPA scripts will
> fetch it, and release a new version of the package (now including the
> malicious code). By requiring tags to be cryptographically signed, we
> can have a greater confidence that any new tag has at the very least
> been signed off by the developer him/herself.
This seems wise to me. Does anyone have arguments against?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
prev parent reply other threads:[~2023-02-26 2:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 18:19 bug#61277: FR: ELPA security - Restrict package builds to signed git commits Daniel Mendler
2023-02-05 11:19 ` 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 [this message]
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=E1pW7GL-0007zb-WE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=61277@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
--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).