linux-kernel - Re: Have RESOLVE_* flags superseded AT

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: <848282.1583159228@warthog.procyon.org.uk>
Date:   Mon, 02 Mar 2020 14:27:08 +0000
From:   David Howells <dhowells@...hat.com>
To:     Christian Brauner <christian.brauner@...ntu.com>
Cc:     dhowells@...hat.com, Florian Weimer <fweimer@...hat.com>,
        linux-api@...r.kernel.org, viro@...iv.linux.org.uk,
        metze@...ba.org, torvalds@...ux-foundation.org, cyphar@...har.com,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Have RESOLVE_* flags superseded AT_* flags for new syscalls?

Christian Brauner <christian.brauner@...ntu.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