netdev - Re: [PATCH net-next] tcp: Namespace-ify sysctl_tcp_default_congestion

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20171114.215707.1588014083788893077.davem@davemloft.net>
Date:   Tue, 14 Nov 2017 21:57:07 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     stephen@...workplumber.org
Cc:     edumazet@...gle.com, netdev@...r.kernel.org, sthemmin@...rosoft.com
Subject: Re: [PATCH net-next] tcp: Namespace-ify
 sysctl_tcp_default_congestion_control

From: Stephen Hemminger <stephen@...workplumber.org>
Date: Mon, 13 Nov 2017 07:37:38 -0800

> The restriction came from earlier discussion with Kees and Eric.
> The security folks are paranoid about containers allowing loading
> of modules. Probably CAP_SYS_MODULE is enough to control this already.

People running tests in namespaces that want to choose a congestion
control algorithm are going to break if you add a new restriction.