From: Andy Wingo <wingo@igalia.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: server and client in one package -> security issue
Date: Tue, 14 Feb 2017 12:19:09 +0100 [thread overview]
Message-ID: <cuc7f4tow9e.fsf@igalia.com> (raw)
In-Reply-To: <58A2DBD0.80905@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 14 Feb 2017 11:28:32 +0100")
On Tue 14 Feb 2017 11:28, Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Am 13.02.2017 um 15:13 schrieb Ludovic Courtès:
>> Now, back to the “only install the required software”, I wouldn’t go as
>> far as you do. I generally agree with the rule, but I’m skeptical as to
>> what this buys you from a security perspective: users can always install
>> whatever they want by hand anyway, and do you have an idea as to how
>> much code they install via their browser?
>
> Looks like we are talking about different systems. I'm talking about
> hardened systems, esp. servers, where users are not allowed to install
> additional software – not even browser add-on.
If the user has no access to the Guix store and daemon, so they can't
even "guix package --install foo", then you're operating on effectively
a snapshot of the store, right? So perhaps you want a facility that
when exporting this store snapshot can remove some subset of files, like
for example the include/ tree on all store directories. But because
this is just an snapshot/export of the store, it doesn't seem necessary
to actually change any particular Guix package to reach your goal, as
far as I understand things anyway.
Andy
next prev parent reply other threads:[~2017-02-14 11:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:43 Add murmur contact.ng0
2017-02-01 20:43 ` [PATCH] gnu: mumble: Add 'murmur' output contact.ng0
2017-02-01 21:15 ` Add murmur ng0
2017-02-09 16:50 ` Ludovic Courtès
2017-02-09 18:20 ` ng0
2017-02-09 22:50 ` Ludovic Courtès
2017-02-10 21:39 ` ng0
2017-02-10 21:54 ` Marius Bakke
2017-02-10 22:15 ` ng0
2017-02-11 14:31 ` Ludovic Courtès
2017-02-11 14:39 ` ng0
2017-02-12 13:37 ` Ludovic Courtès
2017-02-12 13:53 ` ng0
2017-02-12 13:57 ` David Craven
2017-02-12 14:02 ` ng0
2017-02-12 14:37 ` David Craven
2017-02-12 17:01 ` Hartmut Goebel
2017-02-12 17:42 ` pelzflorian (Florian Pelz)
2017-02-13 14:15 ` Ludovic Courtès
2017-02-12 17:54 ` David Craven
2017-02-14 10:13 ` Hartmut Goebel
2017-02-14 9:00 ` ng0
2017-02-12 12:23 ` server and client in one package -> security issue (was: Add murmur) Hartmut Goebel
2017-02-12 12:31 ` ng0
2017-02-12 12:53 ` David Craven
2017-02-12 16:52 ` server and client in one package -> security issue Hartmut Goebel
2017-02-13 14:13 ` Ludovic Courtès
2017-02-14 10:28 ` Hartmut Goebel
2017-02-14 11:19 ` Andy Wingo [this message]
2017-02-14 9:16 ` server and client in one package -> security issue (was: Add murmur) Danny Milosavljevic
2017-02-14 9:51 ` ng0
2017-02-14 10:44 ` server and client in one package -> security issue Hartmut Goebel
2017-04-24 7:01 ` Maxim Cournoyer
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cuc7f4tow9e.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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/guix.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).