[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110225.104720.71110261.davem@davemloft.net>
Date: Fri, 25 Feb 2011 10:47:20 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: segoon@...nwall.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kuznet@....inr.ac.ru, pekkas@...core.fi, jmorris@...ei.org,
yoshfuji@...ux-ipv6.org, kaber@...sh.net, eric.dumazet@...il.com,
therbert@...gle.com, xiaosuo@...il.com, jesse@...ira.com
Subject: Re: [PATCH] don't allow CAP_NET_ADMIN to load non-netdev kernel
modules
From: Vasiliy Kulikov <segoon@...nwall.com>
Date: Fri, 25 Feb 2011 18:14:14 +0300
> Since a8f80e8ff94ecba629542d9b4b5f5a8ee3eb565c any process with
> CAP_NET_ADMIN may load any module from /lib/modules/. This doesn't mean
> that CAP_NET_ADMIN is a superset of CAP_SYS_MODULE as modules are limited
> to /lib/modules/**. However, CAP_NET_ADMIN capability shouldn't allow
> anybody load any module not related to networking.
Why go through this naming change, which does break things, instead of
simply adding a capability mask tag or similar to modules somehow. You
could stick it into a special elf section or similar.
Doesn't that make tons more sense than this?
--
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