netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Stephen Hemminger <stephen.hemminger@vyatta.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Chris Wright <chrisw@linux-foundation.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] sysctl: permission check based on capability not euid
Date: Wed, 28 May 2008 13:14:00 -0700	[thread overview]
Message-ID: <20080528201400.GG30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080528121200.54c04b5a@speedy>

* Stephen Hemminger (stephen.hemminger@vyatta.com) wrote:
> This patch modifies the permission checks for sysctl's from being based on uid=0 (root)
> to use the capability system. This matches the behavior of other OS's using sysctl's
> and capabilities. Linux has tried to get away from using uid=0 for security overrides
> and use capabilities instead. 
> 
> I was working on Quagga enhancement that involved enabling a sysctl, and it didn't
> work because is a safe daemon and drops privileges and resets its real/effective uid
> after initialization; it then re-enables only the capabilities when it needs to
> do some privileged operation. This wouldn't work because sysctl's were still using
> the root based permission check. The existing code in quagga to enable ip forwarding
> doesn't work for the same reason.

I don't think CAP_SYS_ADMIN makes sense for net.*, for example.

      reply	other threads:[~2008-05-28 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 19:12 [PATCH] sysctl: permission check based on capability not euid Stephen Hemminger
2008-05-28 20:14 ` Chris Wright [this message]

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=20080528201400.GG30402@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=akpm@linux-foundation.org \
    --cc=chrisw@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen.hemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).