linux-kernel - Re: O_CAREFUL flag to disable open() side effects

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: <a36005b50607271050g7d6fcf59g4950410e7c9356c4@mail.gmail.com>
Date:	Thu, 27 Jul 2006 10:50:38 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Pekka J Enberg" <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	akpm@...l.org, viro@...iv.linux.org.uk, tytso@....edu,
	tigran@...itas.com
Subject: Re: O_CAREFUL flag to disable open() side effects

On 7/27/06, H. Peter Anvin <hpa@...or.com> wrote:
> Dumb thought: would it make sense to add an O_CAREFUL flag to open(), to
> disable side effects?

Not that I don't want to be constructive, but this is something you'll
likely never be able to specify with the needed level of accuray.
What is careful?  I can imagine all kinds ideas possible ways file
systems and device drivers might want to use this.

Adding a separate interface taking a file name isn't high enough a
price to open such a can of worms.
-
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/