linux-kernel - Re: [TOMOYO #9 (2.6.27-rc7-mm1) 1/6] LSM adapter functions.

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]

Message-ID: <48E975A7.2050000@nttdata.co.jp>
Date:	Mon, 06 Oct 2008 11:19:19 +0900
From:	Kentaro Takeda <takedakn@...data.co.jp>
To:	"Serge E. Hallyn" <serue@...ibm.com>
CC:	Valdis.Kletnieks@...edu, Casey Schaufler <casey@...aufler-ca.com>,
	linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org, haradats@...data.co.jp,
	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
	Al Viro <viro@...IV.linux.org.uk>
Subject: Re: [TOMOYO #9 (2.6.27-rc7-mm1) 1/6] LSM adapter functions.

Serge E. Hallyn wrote:
> Why can't you just clear the value during security_inode_foo()?
We need a new hook for clearing the value since security_inode_*() 
are not always called after security_path_*() .

> Note I'm seeing this as a way for Tomoyo to temporarily (maybe) work
> around the mis-placement of the security_path_foo() hooks.  I don't want
> to add security_path_clear() hooks to "legitimize" the workaround.  I'd
> rather Tomoyo and Apparmor folks keep looking for a better way to get
> real DAC-before-MAC.
Hmm, I can understand your opinion. The best way for AppArmor and 
TOMOYO is to pass vfsmount to vfs_*() and security_inode_*() . This 
approach has no DAC-before-MAC problem. However, it is clearly 
opposed by Al because of layering. So, we are going forward 
security_path_*() approach, which Al advised us.

Since vfsmount is only available outside vfs_*() (and vfs_*() perform 
DAC), we cannot conceive another place now... Where do you think the 
right place to introduce security_path_*() hooks is?

Regards,

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