From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Satyam Sharma <satyam@infradead.org>,
Jan Engelhardt <jengelh@computergmbh.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NFS4 authentification / fsuid
Date: Fri, 7 Sep 2007 11:34:08 -0400 [thread overview]
Message-ID: <20070907153408.GG24638@fieldses.org> (raw)
In-Reply-To: <1189121572.6672.36.camel@heimdal.trondhjem.org>
On Fri, Sep 07, 2007 at 01:32:52AM +0200, Trond Myklebust wrote:
> Sorry. Of course, you have to copy the entire /lib, etc. onto the tmpfs,
> but you get the gist....
>
> The point is that it is easy to subvert userspace if you have enough
> privileges. In the above example it may not be entirely undetectable,
> but who here is running a script on every login to check that / is
> indeed uncompromised?
I suppose this is the motivation for things like the "secure attention
key"?
But I'm most curious actually about to what degree the kernel itself is
vulnerable to root (without a reboot). Is disabling /dev/kmem and
module-loading in theory enough? (Modulo bugs like filesystems that
aren't secure against untrusted filesystems, etc.)
--b.
next prev parent reply other threads:[~2007-09-07 15:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 14:12 NFS4 authentification / fsuid Jan Engelhardt
2007-08-30 14:29 ` Trond Myklebust
2007-08-30 14:32 ` Trond Myklebust
2007-08-30 14:42 ` Jan Engelhardt
2007-08-30 15:04 ` Trond Myklebust
2007-08-30 21:44 ` J. Bruce Fields
2007-09-06 8:14 ` Satyam Sharma
2007-09-06 8:29 ` Satyam Sharma
2007-09-06 15:11 ` J. Bruce Fields
2007-09-06 23:21 ` Trond Myklebust
2007-09-06 23:32 ` Trond Myklebust
2007-09-07 15:34 ` J. Bruce Fields [this message]
2007-09-18 23:27 ` Satyam Sharma
2007-09-18 23:12 ` Satyam Sharma
2007-09-06 15:06 ` J. Bruce Fields
2007-09-06 23:30 ` Kyle Moffett
2007-09-06 23:35 ` Trond Myklebust
2007-09-07 0:56 ` Kyle Moffett
2007-09-07 5:14 ` Trond Myklebust
2007-09-07 5:47 ` Kyle Moffett
2007-09-07 6:37 ` Bernd Eckenfels
2007-09-18 23:48 ` Satyam Sharma
2007-09-18 23:44 ` Satyam Sharma
2007-09-19 5:16 ` Kyle Moffett
2007-09-19 12:16 ` Satyam Sharma
2007-09-19 13:49 ` Kyle Moffett
2007-09-19 14:12 ` Satyam Sharma
2007-09-19 15:01 ` J. Bruce Fields
2007-09-20 7:03 ` Satyam Sharma
2007-09-19 16:38 ` Valdis.Kletnieks
2007-09-20 7:15 ` Satyam Sharma
2007-08-30 15:12 ` J. Bruce Fields
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=20070907153408.GG24638@fieldses.org \
--to=bfields@fieldses.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@infradead.org \
--cc=trond.myklebust@fys.uio.no \
/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