net: Use ns_capable_noaudit() when determining net sysctl permissions
authorTyler Hicks <tyhicks@canonical.com>
Fri, 30 Sep 2016 22:24:31 +0000 (15:24 -0700)
committerDavid S. Miller <davem@davemloft.net>
Sat, 1 Oct 2016 07:24:28 +0000 (03:24 -0400)
commitd6169b0206db1c8c8d0e4c6b79fdf4b2fc6455f1
tree66afc6f21934251d8a661176cf4c33c5743f903b
parent803783849fed11e38a30f31932c02c815520da70
net: Use ns_capable_noaudit() when determining net sysctl permissions

The capability check should not be audited since it is only being used
to determine the inode permissions. A failed check does not indicate a
violation of security policy but, when an LSM is enabled, a denial audit
message was being generated.

The denial audit message caused confusion for some application authors
because root-running Go applications always triggered the denial. To
prevent this confusion, the capability check in net_ctl_permissions() is
switched to the noaudit variant.

BugLink: https://launchpad.net/bugs/1465724
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>
[dtor: reapplied after e79c6a4fc923 ("net: make net namespace sysctls
belong to container's owner") accidentally reverted the change.]
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/sysctl_net.c