| 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: <20090327003040.GH29836@elf.ucw.cz> Date: Fri, 27 Mar 2009 01:30:40 +0100 From: Pavel Machek <pavel@....cz> To: James Morris <jmorris@...ei.org> Cc: kernel list <linux-kernel@...r.kernel.org>, linux-security-module@...r.kernel.org Subject: Re: TOMOYO in linux-next On Fri 2009-03-27 11:15:28, James Morris wrote: > On Thu, 26 Mar 2009, Pavel Machek wrote: > > > Hi! > > > > I don't think merging that is good idea. > > It's already merged in Linus' tree. Too bad. > > Security should be doable > > without making shell-like glob matching... > > The TOMOYO developers have already responded to your feedback on this > issue. It's also an inherent aspect of pathname security, an issue which > has been resolved in favour of inclusion in the kernel. Do you have any references? My memory claims otherwise on this. > As for the rest of the feedback, please work with the developers to fix > any bugs or lack of documentation. Which brings a question: given that kernel<->user interface is undocumented, how was this reviewed? 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