linux-kernel - Re: NFS4 authentification / fsuid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <0D66E86D-8D97-45D7-9C2A-7AB5F42845B5@mac.com>
Date:	Thu, 6 Sep 2007 19:30:25 -0400
From:	Kyle Moffett <mrmacman_g4@....com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	Satyam Sharma <satyam@...radead.org>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: NFS4 authentification / fsuid

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/