From: David Howells <dhowells@redhat.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: dhowells@redhat.com, Florian Weimer <fweimer@redhat.com>,
linux-api@vger.kernel.org, viro@zeniv.linux.org.uk,
metze@samba.org, torvalds@linux-foundation.org,
cyphar@cyphar.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?
Date: Mon, 02 Mar 2020 14:27:08 +0000 [thread overview]
Message-ID: <848282.1583159228@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200302115239.pcxvej3szmricxzu@wittgenstein>
Christian Brauner <christian.brauner@ubuntu.com> wrote:
> > AT_SYMLINK_NOFOLLOW only applies to the last pathname component anyway,
> > so it's relatively little protection.
>
> So this is partially why I think it's at least worth considerings: the
> new RESOLVE_NO_SYMLINKS flag does block all symlink resolution, not just
> for the last component in contrast to AT_SYMLINK_NOFOLLOW. This is
> 278121417a72d87fb29dd8c48801f80821e8f75a
That sounds like a potentially significant UAPI change. What will that break?
David
next prev parent reply other threads:[~2020-03-02 14:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 14:53 Have RESOLVE_* flags superseded AT_* flags for new syscalls? David Howells
2020-02-28 15:24 ` Christian Brauner
2020-02-29 15:26 ` Aleksa Sarai
2020-02-29 15:54 ` Aleksa Sarai
2020-03-01 16:46 ` Christian Brauner
2020-03-01 16:38 ` Christian Brauner
2020-03-02 11:30 ` Florian Weimer
2020-03-02 11:52 ` Christian Brauner
2020-03-02 12:05 ` Christian Brauner
2020-03-02 15:10 ` Christian Brauner
2020-03-02 15:36 ` Aleksa Sarai
2020-03-02 16:31 ` Christian Brauner
2020-03-02 12:09 ` Florian Weimer
2020-03-02 12:19 ` Christian Brauner
2020-03-02 12:35 ` Christian Brauner
2020-03-02 12:42 ` Florian Weimer
2020-03-02 12:55 ` Christian Brauner
2020-03-05 14:33 ` David Howells
2020-03-05 14:38 ` Florian Weimer
2020-03-05 14:43 ` David Howells
[not found] ` <20200305141154.e246swv62rnctite@yavin>
2020-03-05 15:23 ` Christian Brauner
2020-03-02 14:27 ` David Howells [this message]
2020-03-02 14:35 ` Christian Brauner
2020-03-02 14:50 ` David Howells
2020-03-02 15:05 ` Christian Brauner
2020-03-02 15:24 ` Aleksa Sarai
2020-03-02 16:37 ` David Howells
[not found] ` <20200306140032.tpwfytofaeuazalo@yavin>
2020-03-06 14:48 ` David Howells
2020-03-02 15:10 ` Aleksa Sarai
2020-03-02 15:23 ` David Howells
2020-03-02 14:30 ` David Howells
2020-03-02 15:04 ` Aleksa Sarai
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=848282.1583159228@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=cyphar@cyphar.com \
--cc=fweimer@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metze@samba.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.