lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 12 Dec 2012 13:48:30 -0800 From: ebiederm@...ssion.com (Eric W. Biederman) To: nicolas.dichtel@...nd.com Cc: netdev@...r.kernel.org, davem@...emloft.net, aatteka@...ira.com Subject: Re: [RFC PATCH net-next 0/5] Ease netns management for userland ebiederm@...ssion.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 -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists