Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK4o1WytU6BZ+8btvWU3-g+KXwzAz-As0mWxHLHPSSUCY15byA@mail.gmail.com>
Date: Mon, 27 Aug 2012 11:18:07 +0100
From: Justin Cormack <justin@...cialbusservice.com>
To: musl@...ts.openwall.com
Subject: Re: Implementation of sys/capabilities.h

On Mon, Aug 27, 2012 at 10:16 AM, Igmar Palsenberg <musl@...senberg.com> wrote:
> Hi,
>
> I'm in the works of implementing capability support within musl. This we need to implement if you ask me :
>
> cap_init()
> cap_free()
> cap_dup()
> cap_get_flag()
> cap_set_flag()
> cap_clear()
> cap_get_proc()
> cap_set_proc()

Why in Musl out of interest? They are not in other libc's, and people
expect to link to libcap for them surely. And some people argue that
the interfaces are not very well designed (indeed libcap seems to be
adding extra ones not in the withdrawn posix draft), eg see
http://people.redhat.com/sgrubb/libcap-ng/

Justin

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.