From: daw@cs.berkeley.edu (David Wagner)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fcntl.h: define AT_EACCESS
Date: Mon, 19 Apr 2010 22:20:13 +0000 (UTC) [thread overview]
Message-ID: <hqikut$4ts$1@taverner.cs.berkeley.edu> (raw)
In-Reply-To: 20100419215711.GR10984@baikonur.stro.at
Can you share some justification why it's worth extending
faccessat() with new options?
Isn't faccessat() insecure in most use cases, due to TOCTTOU
(time-of-check to time-of-use) vulnerabilities? When faccessat()
returns 0, you learn that at some point in the past, the process had
permission to access a given file, though the process may or may not
have permission at the moment. Why is that a useful thing to know?
I'm sure you're familiar with all the standard arguments why using
access() tends to represent a security vulnerability. Is there a reason
why similar arguments do not apply to faccessat()?
prev parent reply other threads:[~2010-04-19 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 3:08 [PATCH] fcntl.h: define AT_EACCESS maximilian attems
2010-04-19 21:47 ` Andrew Morton
2010-04-19 21:57 ` maximilian attems
2010-04-19 22:10 ` Ulrich Drepper
2010-04-19 22:11 ` H. Peter Anvin
2010-04-19 22:20 ` David Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hqikut$4ts$1@taverner.cs.berkeley.edu' \
--to=daw@cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox