From: ebiederm@xmission.com (Eric W. Biederman)
To: nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, davem@davemloft.net, aatteka@nicira.com
Subject: Re: [RFC PATCH net-next 0/5] Ease netns management for userland
Date: Wed, 12 Dec 2012 13:48:30 -0800 [thread overview]
Message-ID: <87sj7beyc1.fsf@xmission.com> (raw)
In-Reply-To: <87zk1jht7d.fsf@xmission.com> (Eric W. Biederman's message of "Wed, 12 Dec 2012 13:11:02 -0800")
ebiederm@xmission.com (Eric W. Biederman) writes:
> It is very wrong to presume that without context you know the reason for
> the exsitence of any network namespace and that you should or even that
> you can manage it. Think of running your multi-network namespace
> managing application in a container.
A good example of a network namespace you don't want to mess with are
the network namespaces created by vsftp and chrome for security purposes
to remove any possibility of creating new connections to the network.
Eric
next prev parent reply other threads:[~2012-12-12 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 17:17 [RFC PATCH net-next 0/5] Ease netns management for userland Nicolas Dichtel
2012-12-12 17:17 ` [RFC PATCH net-next 1/5] netns: allocate an unique id to identify a netns Nicolas Dichtel
2012-12-12 17:17 ` [RFC PATCH net-next 2/5] netns: allow to dump netns with netlink Nicolas Dichtel
2012-12-12 17:17 ` [RFC PATCH net-next 3/5] dev/netns: allow to get netns from nsindex in rtnl msg Nicolas Dichtel
2012-12-12 17:17 ` [RFC PATCH net-next 4/5] netns: advertise netns activity with netlink Nicolas Dichtel
2012-12-12 17:17 ` [RFC PATCH net-next 5/5] net/sock: add support of SO_NETNS Nicolas Dichtel
2012-12-12 18:39 ` [RFC PATCH net-next 0/5] Ease netns management for userland Nicolas Dichtel
2012-12-12 19:25 ` Eric W. Biederman
2012-12-12 20:54 ` Nicolas Dichtel
2012-12-12 21:11 ` Eric W. Biederman
2012-12-12 21:48 ` Eric W. Biederman [this message]
2012-12-13 17:41 ` Nicolas Dichtel
2012-12-13 19:08 ` Eric W. Biederman
2012-12-14 16:13 ` Nicolas Dichtel
2012-12-14 16:50 ` Eric W. Biederman
2012-12-19 9:47 ` Nicolas Dichtel
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=87sj7beyc1.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=aatteka@nicira.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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.
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.