linux-kernel - Re: [AppArmor 01/41] Pass struct vfsmount to the inode

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:	Tue, 29 May 2007 19:07:29 +0200
From:	Andreas Gruenbacher <agruen@...e.de>
To:	Tetsuo Handa <from-lsm@...ove.sakura.ne.jp>
Cc:	crispin@...ell.com, cliffe@...et.net.au, casey@...aufler-ca.com,
	mrmacman_g4@....com, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSMhook

On Tuesday 29 May 2007 12:46, Tetsuo Handa wrote:
> But, from the pathname-based access control's point of view,
> bind mount interferes severely with pathname-based access control
> because it is impossible to determine which pathname was requested.

Wrong. It is very well possible to determine the path of a particular dentry 
(+ vfsmount) with bind mounts.

> Although both pathnames point to the same object, TOMOYO focuses on the
> PROCEDURE FOR REACHING AN OBJECT and being able to know the procedure is
> very important.

This doesn't make sense, either. With the following sequence of syscalls of 
processes A and B (both of them in the namespace root),

	A:				B:
	mkdir("/tmp/a")
	chdir("/tmp/a")
					rename("/tmp/a", "/tmp/b")
	creat("f")

the path being checked for the creat call must be "/tmp/b/f", even though 
process A never explicitly used "b". If that's not what TOMOYO is doing, then 
that's badly broken.

Andreas
-
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/