unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: 61277@debbugs.gnu.org, yantar92@posteo.net,
	stefankangas@gmail.com, monnier@iro.umontreal.ca
Subject: bug#61277: FR: ELPA security - Restrict package builds to signed git commits
Date: Wed, 15 Feb 2023 00:17:21 -0500	[thread overview]
Message-ID: <E1pSAAT-0002sj-AC@fencepost.gnu.org> (raw)
In-Reply-To: <23c855a2-4330-6da8-6a05-72f26e4ebc5b@daniel-mendler.de> (message from Daniel Mendler on Sun, 12 Feb 2023 11:32:36 +0100)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > There could also be a breach on the server where the git repository is
  > hosted. The repository could be manipulated directly on the server. It
  > is not that likely but if such incidents happen they have a huge
  > fallout. I also expect that more and more people move their
  > :auto-sync'ed git repositories to private servers or smaller forges,
  > which may not be as protected as the most popular ones.

Do we know of any security experts who appeciate the moral principles
of free software, who could help us come up with methods that properly
handle both?

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







  reply	other threads:[~2023-02-15  5:17 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 [this message]
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=E1pSAAT-0002sj-AC@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).