mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Satyam Sharma <satyam@infradead.org>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	Jan Engelhardt <jengelh@computergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NFS4 authentification / fsuid
Date: Thu, 6 Sep 2007 19:30:25 -0400	[thread overview]
Message-ID: <0D66E86D-8D97-45D7-9C2A-7AB5F42845B5@mac.com> (raw)
In-Reply-To: <20070906150616.GA28565@fieldses.org>

On Sep 06, 2007, at 11:06:16, J. Bruce Fields wrote:
> On Thu, Sep 06, 2007 at 01:44:05PM +0530, Satyam Sharma wrote:
>> Like Trond said, there are very high number of ways in which  
>> privileged userspace can compromise a running kernel if it really  
>> wants to do that, root-is-God has always been *the* major problem  
>> with Unix :-)
>>
>> The only _real_ way a kernel can lock itself completely against  
>> malicious userspace involves trusted tamperproof hardware,
>
> The question of how to protect against someone with *physical*  
> access certainly is more difficult, but surely that's a separate  
> problem.

Actually, that's a fairly simple problem (barring disassembling the  
system and attaching a hardware debugger).  You encrypt the root  
filesystem and require a password to boot (See: LUKS).  Debian has  
built-in support for installing onto fs-on-LVM-on-crypt-on-RAID, and  
it works quite well on all the laptops I use regularly.  It's not  
even much of a speed penalty; once you take the overhead of hitting a  
5400RPM laptop drive you can chew thousands of cycles of CPU without  
anybody noticing (much).  Then all you have to do is burn a copy of  
your /boot with bootloader onto some read-only media (like a  
finalized CDROM/DVDROM) and you're set to go.

Cheers,
Kyle Moffett

  reply	other threads:[~2007-09-06 23:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 14:12 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
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 [this message]
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=0D66E86D-8D97-45D7-9C2A-7AB5F42845B5@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=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

all inboxes | Powered by JetHome®