linux-kernel - Re: [patch 1/2] [RFC] Simple tamper-proof device filesystem.

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: <47650C88.6040105@davidnewall.com>
Date:	Sun, 16 Dec 2007 22:01:20 +1030
From:	David Newall <david@...idnewall.com>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
CC:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 1/2] [RFC] Simple tamper-proof device filesystem.

Tetsuo Handa wrote:
> David Newall wrote:
>   
>> Tetsuo Handa wrote:
>>     
>>>  /dev needs to be writable, but this means that files on /dev might be
>>>  tampered with.
>>>       
>> I infer that you mean /dev needs to be writable by anyone, not by just 
>> its owner or owner and group (conventionally root/root.)  This goes 
>> against conventional wisdom, which is that /dev must be writable only by 
>> the administrator.  Why do you say otherwise?
>>     
> I didn't mean that "/dev is writable by everybody".
>   

Glad to hear it! :)

> I meant that "/dev must be mounted for read-write mode"
>   

Again, why?
--
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/