public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David <david@unsolicited.net>
Cc: efault@gmx.de, linux-kernel@vger.kernel.org,
	"Andrew G. Morgan" <morgan@kernel.org>,
	linux-security-module@vger.kernel.org,
	"Serge E. Hallyn" <serue@us.ibm.com>
Subject: Re: 2.6.25 Kernel - Problems with capabilities
Date: Sun, 20 Apr 2008 15:21:57 -0700	[thread overview]
Message-ID: <20080420152157.8c59f8be.akpm@linux-foundation.org> (raw)
In-Reply-To: <480B4E87.4020709@unsolicited.net>

(cc's added)


> On Sun, 20 Apr 2008 15:09:11 +0100 David <david@unsolicited.net> wrote:
> Mike Galbraith wrote:
> > On Sat, 2008-04-19 at 19:43 +0100, David wrote:
> >   
> >> I'm wondering if anyone might be able to help with a capability problem 
> >> I've noticed with .25 My ntp daemon will no longer run as any non-root 
> >> user, and after some investigation it seems that calls to prctl() are 
> >> failing.
> >>
> >> CONFIG_SECURITY_CAPABILITIES=y , so this should work?
> >>
> >> System is 32 bit x86 based on a venerable SuSE 9.1 distro.
> >>
> >> Full .config is attached.
> >>
> >> Thanks
> >> David
> >>
> >>
> >>     
> >
> > FWIW, ntpd runs just fine here as user ntp on both my P4 and Q6600 boxen
> > with opensuse 10.3.
> >
> > marge:..tmp/linux-2.6.25 # grep SECUR .config
> > CONFIG_EXT2_FS_SECURITY=y
> > CONFIG_EXT3_FS_SECURITY=y
> > CONFIG_EXT4DEV_FS_SECURITY=y
> > CONFIG_SECURITY=y
> > CONFIG_SECURITY_NETWORK=y
> > CONFIG_SECURITY_NETWORK_XFRM=y
> > CONFIG_SECURITY_CAPABILITIES=y
> > CONFIG_SECURITY_FILE_CAPABILITIES=y
> > CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
> > # CONFIG_SECURITY_SELINUX is not set
> > marge:..tmp/linux-2.6.25 # grep SECUR /xx
> > CONFIG_EXT2_FS_SECURITY=y
> > CONFIG_EXT3_FS_SECURITY=y
> > CONFIG_REISERFS_FS_SECURITY=y
> > # CONFIG_XFS_SECURITY is not set
> > CONFIG_SECURITY=y
> > CONFIG_SECURITY_NETWORK=y
> > # CONFIG_SECURITY_NETWORK_XFRM is not set
> > CONFIG_SECURITY_CAPABILITIES=y
> > # CONFIG_SECURITY_FILE_CAPABILITIES is not set
> > # CONFIG_SECURITY_ROOTPLUG is not set
> > CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
> >
> > I notice I have CONFIG_SECURITY_FILE_CAPABILITIES set, and you don't.  I
> > have not even the foggiest clue whether that has anything to do with the
> > price of tea in china though :)
> >   
> I've just set
> 
> CONFIG_SECURITY_FILE_CAPABILITIES=y
> CONFIG_SECURITY_NETWORK_XFRM=y
> 
> to no avail.. I still get
> 
> 
> 20 Apr 15:04:20 ntpd[15694]: cap_set_proc() failed to drop root 
> privileges: Invalid argument
> 
> after rebuild & reboot. No massive deal, I'll just run ntpd as root for 
> now, but there's definitely something funny going on.
> 
> Cheers
> David


      parent reply	other threads:[~2008-04-20 22:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 18:43 2.6.25 Kernel - Problems with capabilities David
     [not found] ` <1208676743.4763.10.camel@marge.simson.net>
2008-04-20 14:09   ` David
2008-04-20 17:15     ` Casey Schaufler
2008-04-20 17:29       ` David
2008-04-20 19:08         ` Andi Kleen
2008-04-20 22:04           ` Casey Schaufler
2008-04-20 22:36             ` Andi Kleen
2008-04-21  0:00         ` serge
2008-04-21  0:44           ` Andrew Morgan
2008-04-21  7:20             ` David R
2008-04-21  7:01           ` David R
2008-04-21 18:34             ` serge
2008-04-21 18:48               ` David
2008-04-21 19:01                 ` serge
2008-04-21 20:28                   ` David
2008-04-22  2:42                     ` serge
2008-04-22  5:29                       ` Andrew G. Morgan
2008-04-22  5:54                         ` David R
2008-04-20 22:21     ` Andrew Morton [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=20080420152157.8c59f8be.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=david@unsolicited.net \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=serue@us.ibm.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