From: Igmar Palsenberg <igmar@palsenberg.com>
To: musl@lists.openwall.com
Subject: Re: Implementation of sys/capabilities.h
Date: Mon, 27 Aug 2012 12:23:32 +0200 [thread overview]
Message-ID: <E1330BA1-69FA-444E-A070-6A781638D333@palsenberg.com> (raw)
In-Reply-To: <CAK4o1WytU6BZ+8btvWU3-g+KXwzAz-As0mWxHLHPSSUCY15byA@mail.gmail.com>
>> 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/
It's open for debate. The syscalls need to be there (including the structs the kernel uses), and I've got those in a patch.
I agree the interface is shit : Way to complicated, while only need some simple functions, with a bitmap to represent them. Why implement it ?
It's the only thing we got, and programs assume it's POSIX, so it should be present. Yes, it's broken, but capabilities are a needed feature if you ask me.
Igmar
next prev parent reply other threads:[~2012-08-27 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 9:16 Igmar Palsenberg
2012-08-27 10:18 ` Justin Cormack
2012-08-27 10:23 ` Igmar Palsenberg [this message]
2012-08-27 11:26 ` Justin Cormack
2012-08-27 11:38 ` Igmar Palsenberg
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=E1330BA1-69FA-444E-A070-6A781638D333@palsenberg.com \
--to=igmar@palsenberg.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).