From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 32544@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#32544: [ELPA] core packages need generated files
Date: Tue, 28 Aug 2018 07:54:46 -0400 [thread overview]
Message-ID: <jwvtvnen1y0.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <u45zzvck7h.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 27 Aug 2018 22:13:06 -0400")
>> I think the reasons why I'm more worried about elpa.gnu.org than the
>> end-user's machines include:
>>
>> - very little time between the moment we receive the commit-diffs by
>> email and the moment the code is run. So even if we notice the
>> offending code on the spot, there's not much time to react.
>> - elpa.gnu.org is part of infrastructure that Emacs users trust when
>> downloading GNU ELPA packages (e.g. it holds the PGP signing key), so
>> a breach could affect all GNU ELPA users (especially if not
>> noticed).
One more reason:
- elpa.gnu.org *can* run that code in a sandbox, whereas the end-user
really wants to run the package's code in his "real" system (or
otherwise would need to run his whole Emacs session in a sandbox).
> Sounds very sensible, best of luck! :)
Hmm... looks like you forgot to attach the patch to your message.
Could you send it again, please?
Stefan
next prev parent reply other threads:[~2018-08-28 11:54 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
2018-08-28 0:15 ` Stefan Monnier
2018-08-28 2:13 ` Glenn Morris
2018-08-28 11:54 ` Stefan Monnier [this message]
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=jwvtvnen1y0.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=32544@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=rgm@gnu.org \
/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).