[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120906034146.GB27715@brightrain.aerifal.cx>
Date: Wed, 5 Sep 2012 23:41:46 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: capset() capget() syscalls
On Wed, Sep 05, 2012 at 11:28:11PM -0400, Kurt H Maier wrote:
> On Wed, Sep 05, 2012 at 11:20:13PM -0400, Rich Felker wrote:
> >
> > Thanks for the input, but I don't think it's quite that clear-cut and
> > I don't have a good answer. There should be some way to access
> > capabilities without needing an ugly library which allocates dynamic
> > memory to report the current capability set (yes, libcap is THAT bad),
> > but the sys/capabilities.h interfaces are also a complete mess...
> >
>
> Why not replace libcap instead of doing this in musl?
That's kind of the direction I was thinking. And the "portable" (to
all known Linux libcs) way to do this would be using <sys/syscall.h>
and SYS_capset/SYS_capget to implement such a library, rather than
having special-case code to do X on glibc and Y on musl...
Alternatively, if the kernel and glibc folks could agree (or at least
the glibc folks), we could develop a new sane API for exposing
capabilities from libc instead of with a third-party library.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
