mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	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, 07 Sep 2007 07:14:09 +0200	[thread overview]
Message-ID: <1189142049.6681.29.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <5B1FC03A-6819-4C6C-91D3-F3022B798EF4@mac.com>

On Thu, 2007-09-06 at 20:56 -0400, Kyle Moffett wrote:
> On Sep 06, 2007, at 19:35:14, Trond Myklebust wrote:
> > On Thu, 2007-09-06 at 19:30 -0400, Kyle Moffett wrote:
> >> 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.
> >
> > Disconnect battery, and watch boot password go 'poof!'.
> 
> Umm, I did say "encrypt the root filesystem", didn't I?  Booting my  
> laptops this way follows this procedure:
>    1) Enter BIOS boot menu
>    2) Insert /boot CDROM
>    3) Select the "CDROM" entry
>    4) Wait for kernel to start and run through initramfs
>    5) Type password into the initramfs prompt so that it can DECRYPT  
> THE ROOT FILESYSTEM
>    6) Continue to boot the system.
> 
> Under this setup, tinkering with my BIOS does virtually nothing; the  
> only avenues of attack are strictly of the "Install a hardware  
> keylogger" variety.  Without my "boot" password you are looking at a  
> block device which appears to be little more than a random bit- 
> bucket, using AES-256 encryption.  If you can break that by  
> disconnecting the BIOS battery a lot of governments would be very  
> interested in the exact procedure. :-D  Furthermore if I think that  
> the hardware has been compromised I can pull out the HDD and my CDROM  
> and take them to a trusted computer to gain access to my data.
> 
> That said, a useful BIOS password helps keep somebody from casually  
> setting a supervisor password or mucking with the critical-to-boot  
> settings and making _me_ unplug the battery.
> 
> Cheers,
> Kyle Moffett

So an attacker will instead install a hardware keylogger, or swap out
your boot cdrom with a compromised but almost identical boot cdrom
instead, or mod your bios, ...

A fully self-certifying system that can prevent any attack is _very_
hard to achieve. Just ask apple (iPhone) or any games console vendor...

Trond


  reply	other threads:[~2007-09-07  5:14 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
2007-09-06 23:35                 ` Trond Myklebust
2007-09-07  0:56                   ` Kyle Moffett
2007-09-07  5:14                     ` Trond Myklebust [this message]
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=1189142049.6681.29.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=bfields@fieldses.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=satyam@infradead.org \
    /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®