linux-kernel - Need for llistxattrat()/lgetxattrat()/lsetxattrat()

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>] [day] [month] [year] [list]

Message-ID: <1374870482.15230.55.camel@localhost>
Date:	Fri, 26 Jul 2013 16:28:02 -0400
From:	Colin Walters <walters@...bum.org>
To:	linux-kernel@...r.kernel.org
Cc:	Al Viro <viro@...iv.linux.org.uk>
Subject: Need for llistxattrat()/lgetxattrat()/lsetxattrat()

Hi,

So at the moment the kernel has pretty comprehensive support for the
*at() variants of file API calls, and at one point I was rewriting my
app to be a modern Unix citizen and use the *at variants, but I ran into
one admittedly obscure corner case, which is the lack of API calls to
manipulate the extended attributes of symbolic links relative to a
dirfd.  

Correctly handling xattrs (in particular, SELinux labels) is a key part
of my application, so for now I'll just live with pathnames and their
drawbacks, but:

Is this intentional or an oversight?  If the latter, should I try a
patch?

--
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/