| 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
| ||
|
Message-ID: <355270241.1702481236702404399.JavaMail.root@spooler8-g27.priv.proxad.net> Date: Tue, 10 Mar 2009 17:26:44 +0100 (CET) From: porte64@...e.fr To: linux-kernel@...r.kernel.org Subject: read-only partitions: does the policy apply to all metadata ? Hello, When a partition is mounted as read-only, does the kernel really prevent ANY byte to be written to it, including any metadata ? (i am thinking here about file attributes -- last access time, as well as meta information about filesystem/blocks description etc ...). And is the policy implemented in every filesystem type driver or at some abstraction level (as if the write() and like system calls were designed to return an error). Unfortunately, on common (all?) hard drives, there seems to be no switch to set the device microcode in read-only mode. By the way, this makes me also thing about memory cards with locks: is it a real protection or it is just a setting which tells the kernel that it *SHOULD* mount the device read-only ? Please include my private address if you answer; i posted to the list because in some other forums we did not come up with a clear answer, so this is my last chance to get a definite done. However i didn't subscribe to the list as i have realized i am not able to help unfortunately: operating systems are the most complex thing ever design by humans ! Best regards Phil -- 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/
Powered by blists - more mailing lists