From: Ricardo Wurmus <rekado@elephly.net>
To: Ryan Prior <ryanprior@hey.com>
Cc: guix-devel@gnu.org
Subject: Re: Login to a guix container
Date: Mon, 25 Jan 2021 08:29:32 +0100 [thread overview]
Message-ID: <87pn1tjwyr.fsf@elephly.net> (raw)
In-Reply-To: <9aa892b1c2ec59b15417a5871f1b83d481ab3419@hey.com>
Ryan Prior <ryanprior@hey.com> writes:
> On January 24, 2021, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
>> I was just thinking that it should be possible to login with ssh into
>> a GNU Guix shell running in a container that gets fired up by the
>> sshd. I am thinking about a safe shell for fetching files. If this
>> works no chroot setup is required.
>>
>> Or is this a really dumb idea :)
>
> I haven't seen any serious audit investigating security properties of
> Guix containers. I do not think it's dumb to try this as an experiment,
> but I do think it would be malpractice to trust user data with this
> system before appropriately thorough evaluation.
In your requirements for an audit, how does a “Guix container” differ
from a “Linux container”? Guix uses the kernel features like cloning
namespaces and unsharing the filesystem directly. It merely mounts
individual store locations into the filesystem namespace.
“Malpractice” is a very big word for using user namespaces instead of
chroot without a “serious audit”.
--
Ricardo
next prev parent reply other threads:[~2021-01-25 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 22:05 Login to a guix container Pjotr Prins
2021-01-25 1:41 ` Ryan Prior
2021-01-25 7:29 ` Ricardo Wurmus [this message]
2021-01-25 8:30 ` Pjotr Prins
2021-01-25 11:01 ` Ricardo Wurmus
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=87pn1tjwyr.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ryanprior@hey.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).