From: Christopher Baines <mail@cbaines.net>
To: Zhu Zihao <all_but_last@163.com>
Cc: help-guix@gnu.org
Subject: Re: Port forwarding for Guix containers
Date: Fri, 20 Nov 2020 19:26:00 +0000 [thread overview]
Message-ID: <871rgnltiv.fsf@cbaines.net> (raw)
In-Reply-To: <28690cfe.8dc4.175e13a4596.Coremail.all_but_last@163.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
Zhu Zihao <all_but_last@163.com> writes:
> I found guix container "created by `guix environment --container` or
> `guix system container`" is very useful to isolate some service. But
> it only supports fully isolated network namespace or just share with
> host, it's not so safe IMO.
I'll assume that a fully isolated network namespace is safer in whatever
way you're referring to than a shared network namespace. However, for a
shared network namespace, what threats is that not safe in respect to?
In the shared network namespace scenario, you are free to use a
firewall, which could help protect against threats coming from other
machines, for example by creating a list of IP addresses which are
allowed to connect, and dropping any other traffic.
If it's not on another machine, but on the same machine, there's
probably more to worry about than the network if you're assuming another
process is malicious, it could potentially escape from the isolation put
in place by Linux, or use excessive resources to attempt to disrupt
other processes.
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2020-11-20 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 15:58 Port forwarding for Guix containers Zhu Zihao
2020-11-20 18:44 ` Bonface M. K.
2020-11-20 19:26 ` Christopher Baines [this message]
2020-11-21 14:53 ` zimoun
2020-11-21 20:20 ` Edouard Klein
2020-11-21 21:45 ` Jason Conroy
2020-11-22 15:09 ` edk
2020-11-23 14:58 ` Jason Conroy
2020-11-23 16:16 ` Zhu Zihao
2020-11-23 16:21 ` Zhu Zihao
2020-11-25 16:14 ` Jason Conroy
2020-12-03 9:32 ` Zhu Zihao
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rgnltiv.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=all_but_last@163.com \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.