linux-kernel - Re: [RFC PATCH] vfs: new open(2) flag to open filesystem node

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 06 Jul 2009 14:29:55 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	drepper@...il.com
CC:	torvalds@...ux-foundation.org, miklos@...redi.hu,
	dhowells@...hat.com, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, hch@...radead.org,
	viro@...iv.linux.org.uk, adilger@....com, alan@...rguk.ukuu.org.uk,
	akpm@...ux-foundation.org, mtk.manpages@...il.com
Subject: Re: [RFC PATCH] vfs: new open(2) flag to open filesystem node

On Sun, 5 Jul 2009, Ulrich Drepper wrote:
> On Sun, Jul 5, 2009 at 17:40, Linus
> Torvalds<torvalds@...ux-foundation.org> wrote:
> > O_SEARCH is only meaningful for directories. For anything else, it's not
> > at all POSIX - it's expressly defined to be "undefined".
> 
> And this is why there is the differentiation with O_EXEC.  Yes, i
> didn't mention it in the last email.  But I mentioned it when it came
> up the first time.
> 
> I don't say this is indeed what is wanted/needed here.  But there are
> IMO some similarities and I think implementing O_SEARCH and O_EXEC is
> desirable.

O_SEARCH loosens the security model somewhat: a process could keep
search access to a directory even after the permissions have been
changed.

O_EXEC is similar, but "execute" is really not an access, just a flag,
so...

Thanks,
Miklos
--
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/