linux-kernel - Re: [RFC] O_NOACC: open without any access

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:	Wed, 24 Jun 2009 20:06:08 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	drepper@...il.com
CC:	miklos@...redi.hu, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	viro@...iv.linux.org.uk, adilger@....com, dhowells@...hat.com,
	alan@...rguk.ukuu.org.uk, akpm@...ux-foundation.org
Subject: Re: [RFC] O_NOACC: open without any access

On Wed, 24 Jun 2009, Ulrich Drepper wrote:
> On Wed, Jun 17, 2009 at 23:55, Miklos Szeredi<miklos@...redi.hu> wrote:
> > The sole purpose is to help race free "userspace lookup" type
> > operations.  So fstat, fch*, *at work but nothing else.  Filesystem's
> > ->open() is not called and f_op is set to NULL.
> 
> Before adding something like this, please look at the 2009 POSIX spec.

Is it available online somewhere?  If not, could you please post the
relevant parts?

>  There are two new open() flags which have to be implemented: O_EXEC
> and O_SEARCH.  These might already suffice for what you want.

I suspect they are not quite what we want (both of them requring
MAY_EXEC on file, no?)

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/