| 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: <ac3eb2510905111405y5541117euf84dd38d39012bd0@mail.gmail.com> Date: Mon, 11 May 2009 23:05:59 +0200 From: Kay Sievers <kay.sievers@...y.org> To: "David P. Quigley" <dpquigl@...ho.nsa.gov> Cc: Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>, Jan Blunck <jblunck@...e.de> Subject: Re: [patch 00/13] devtmpfs patches On Mon, May 11, 2009 at 22:41, David P. Quigley <dpquigl@...ho.nsa.gov> wrote: > This however does highlight a problem with the fact that device node > labeling isn't being done properly. It should be possible to create this > fs with a different name such that it doesn't appear as a tmpfs file > system to SELinux. If it appears as a devtmpfs file system then we can > specify the root label and labels on the other devices properly in > policy. That could be done, if it solves this problem. Damn, now we have the naming problem back again. :) By doing its own fstype, we could also make the auto-mount optional, because you could always reach the filesystem anytime later. A different fstype has the slight inconvenience, that existing userspace needs to be taught to handle it explicitly, while a tmfps is already handled automatically because we use tmpfs already today. But that may not be too important. Thanks a lot for your tests and analysis, Kay -- 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