unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 61277@debbugs.gnu.org, stefan@marxist.se, monnier@iro.umontreal.ca
Subject: bug#61277: FR: ELPA security - Restrict package builds to signed git commits
Date: Sun, 05 Feb 2023 11:19:59 +0000	[thread overview]
Message-ID: <87a61se4v4.fsf@localhost> (raw)
In-Reply-To: <87pmapqoo5.fsf@daniel-mendler.de>

Daniel Mendler <mail@daniel-mendler.de> writes:

> 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)?

I think that requiring every single commit to be signed is an overkill.
Maybe just the release tags?

I guess, :signature, if optional, may allow multiple levels of
verification:
1. nil :: no verification
2. (tags key1 key2 ...) :: verify release tags to match any of the
   listed GPG keys
3. (commits key1 key2 ...) :: verify every commit   

I am not sure what would be the most reliable way to specify the keys.

Also, people with write access to ELPA repo may be required to sign
their commits -- in the case of security breach if the SSH key gets
stolen, signing may be a barrier to protect altering the elpa-packages
configuration from injecting malicious GPG keys.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2023-02-05 11:19 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 [this message]
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=87a61se4v4.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=61277@debbugs.gnu.org \
    --cc=mail@daniel-mendler.de \
    --cc=monnier@iro.umontreal.ca \
    --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).