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
| ||
|
Date: Fri, 18 Sep 2015 11:00:17 -0400 From: Drew DeVault <sir@...wn.com> To: Ortwin Glück <odi@....ch>, Richard Weinberger <richard@....at> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Failover root devices > I personally think this is opening a can of worms. Now it's just a list > of alternative root devices. But the kernel knows absolutely nothing > about these. When is it fine to try an alternative? Why did the first > one not work? Did we just not wait long enough? Or is it a failed RAID > device? Or is it an encrypted disk that needs setup? Or is it on NFS and > the network is not available (or we are lacking driver firmware)? I don't think these are problems that aren't already inherent in a single root device via root=. > It could actually introduce security problems: if I know that a device > will fallback to an alternative root (under my control), I can try and > DOS the primary root. If you have physical access then the machine is yours to do with as you please. -- Drew DeVault -- 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