From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: Geoffrey McRae <geoff@rabidhost.com>,
Nick Andrew <nick@nick-andrew.net>,
linux-kernel@vger.kernel.org
Subject: Re: New Security Features, Please Comment
Date: Thu, 4 Dec 2008 00:08:58 +0000 [thread overview]
Message-ID: <20081204000858.6c79003a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1228347564.10407.18.camel@localhost.localdomain>
> Well, in this particular case, and with this API, perhaps not.
ptrace, patching your own binary, kill etc.
> It would be great if you could say 'limit setuid() to saved-uid + uids
> 1000-2000' or something like that.
For the fsuid
> If then the userlevel NFS server gets owned you can at least be sure
> none of the files in /bin have been modified ..
The userland nfsd uses fsuid.. thats important. Acting on behalf of
another user for file purposes does make sense. I can see a
"setfsuidlist()" call making sense too, but uid/euid/saved uid don't make
sense in this context.
Alan
prev parent reply other threads:[~2008-12-04 0:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 23:28 Geoffrey McRae
2008-12-03 0:24 ` Geoffrey McRae
2008-12-03 0:53 ` Alan Cox
2008-12-03 1:44 ` Geoffrey McRae
2008-12-03 2:11 ` David Newall
2008-12-03 2:55 ` Valdis.Kletnieks
2008-12-03 4:02 ` Geoffrey McRae
2008-12-03 4:35 ` Peter Teoh
2008-12-03 5:02 ` Geoffrey McRae
2008-12-03 6:54 ` David Newall
2008-12-03 10:29 ` Alan Cox
2008-12-03 12:42 ` Nick Andrew
2008-12-03 12:46 ` Alan Cox
2008-12-03 22:44 ` Geoffrey McRae
2008-12-03 23:08 ` Alan Cox
2008-12-03 23:27 ` Peter Teoh
2008-12-03 23:40 ` Geoffrey McRae
2008-12-04 21:56 ` Valdis.Kletnieks
2008-12-04 22:30 ` Geoffrey McRae
2008-12-05 3:35 ` Valdis.Kletnieks
2008-12-05 3:44 ` Nick Andrew
2008-12-05 3:50 ` Geoffrey McRae
2008-12-05 4:03 ` Valdis.Kletnieks
2008-12-03 23:39 ` Miquel van Smoorenburg
2008-12-04 0:00 ` Geoffrey McRae
2008-12-04 0:22 ` Peter Teoh
2008-12-04 0:08 ` Alan Cox [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=20081204000858.6c79003a@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=geoff@rabidhost.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
--cc=nick@nick-andrew.net \
/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
all inboxes | Powered by JetHome®