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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAG27Bk1qet6r72-FPSp8K+9qA3rGQ3Wfu5gPUyNfgzMOfLVeHw@mail.gmail.com>
Date:   Sat, 19 Aug 2017 15:56:54 +0100
From:   Sami Kerola <kerolasa@....fi>
To:     linux-kernel@...r.kernel.org
Subject: devtmpfs: regular files

Hi,

Is there some reason why devtmpfs allows creation of regular files? I
think it would be nice if /dev would behave same way as /proc, that
is:

$ echo example > /proc/regular-file.txt
-bash: /proc/regular-file.txt: No such file or directory

That would make users who rm /dev/null to notice something is wrong
before all space is taken by some rubbish writer. Secondly when /dev/
is used for pairing daemons with fifo this would make incorrect start
order to fail without intervention needed - no more writer creating a
file, and reader that wants to use same path for fifo being unable to
do so.

This could be a mount option. Something like nofile in spirit of nodev
but with opposite effect. My assumption is that changing default
behavior is unlikely to be approvable.

-- 
Sami Kerola
http://www.iki.fi/kerolasa/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ