unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 32544@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#32544: [ELPA] core packages need generated files
Date: Mon, 27 Aug 2018 19:31:07 -0400	[thread overview]
Message-ID: <4dh8jfo090.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvh8jfu9an.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 27 Aug 2018 11:21:16 -0400")

Stefan Monnier wrote:

> The main issue is to make it possible to build those files on
> elpa.gnu.org without too many security risks.
>
> I planned to do that by running "make" inside an LXC container, but my
> attempts to make a lightweight LXC container on elpa.gnu.org failed
> se far.

Is the concern privilege escalation in build recipes in malicious elpa
packages?

But couldn't the same package run the same bad code at package install
time on the end user's machine, today and for as long as elpa.gnu.org
has existed?

Ie, if we assume malicious code can get into elpa packages with no-one
noticing, the whole system is already broken anyway?

So would it be good enough in practice to avoid accidental damage by
running make as a dedicated elpa-build user with no special privs?

But if you want to make the elpa system more secure one piece at a time,
that's obviously no bad thing.





  parent reply	other threads:[~2018-08-27 23:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 15:05 bug#32544: [ELPA] core packages need generated files Michael Albinus
2018-08-27 15:21 ` Stefan Monnier
2018-08-27 15:34   ` Michael Albinus
2018-08-27 15:52     ` Stefan Monnier
2018-08-28 15:17       ` Philippe Vaucher
2018-08-27 23:31   ` Glenn Morris [this message]
2018-08-28  0:15     ` Stefan Monnier
2018-08-28  2:13       ` Glenn Morris
2018-08-28 11:54         ` Stefan Monnier
2020-12-20 17:20   ` Stefan Monnier

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=4dh8jfo090.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=32544@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@IRO.UMontreal.CA \
    /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).