linux-kernel - private user<->kernel interface in linux-2.6.30, was Re: TOMOYO in linux-next

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Mar 2009 12:41:48 +0100
From:	Pavel Machek <pavel@....cz>
To:	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:	jmorris@...ei.org, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org
Subject: private user<->kernel interface in linux-2.6.30, was Re: TOMOYO in
	linux-next

Hi!


> > That's my main complaint: Documentation.*tomoyo nor
> > Documentation.*TOMOYO does not exist, still this adds a *lot* of new
> > user<->kernel interfaces.
> > 
> > New user<->kernel interaces should be documented and very carefuly
> > reviewed; I don't think that happened here.
> These user<->kernel interface are for TOMOYO's policy management tools,
> not for general userland applications like /bin/bash /usr/sbin/sshd etc.

I do believe all user<->kernel interfaces should be properly
reviewed/documented. We'll have to maintain them forever. Just because
you don't intend them to be used by /bin/bash does not mean people
will not use them; and it does not mean we will not have to carry them
forever.

							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/