| 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: <20081104202011.GA7135@ucw.cz> Date: Tue, 4 Nov 2008 21:20:11 +0100 From: Pavel Machek <pavel@...e.cz> To: Kay Sievers <kay.sievers@...y.org> Cc: Michael Tokarev <mjt@....msk.ru>, Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: data corruption: revalidating a (removable) hdd/flash on re-insert > >> Every access to removable media is guarded by this revalidation check. > >> If you don't see these events, you should not trust this reader, and > >> at least never change the media while it is connected. > > > > This is rather nasty data-corrupter. > > Sure, it is. > > > Could we at least blacklist > > broken device, and force revalidation on each close or something like > > that? > > What's your idea of revalidation if the hardware does not tell you? > Get an md5 of the disk content? :) Well... you should not eject media while fs is mounted or blockdev is open, correct? So can we simply claim 'media changed' on last close/unmount? Sure, sometimes media was not changed, but that only hurts performance, not correctness... ? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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