From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] Renaming the caps USE flag to libcap
Date: Fri, 07 Mar 2008 15:34:02 +0100 [thread overview]
Message-ID: <fqrjoq$eaq$1@ger.gmane.org> (raw)
In-Reply-To: m24pbj7eru.fsf@gmail.com
Diego 'Flameeyes' Pettenò wrote:
>
> I'd like to propose the rename of caps USE flag to libcap. The reason
> for this is that I'd like to free the "caps" USE flag from the (runtime)
> dependency of libcap, so that, one we have the framework to do so, we
> could use the "caps' USE flag to set file capabilities directly (rather
> than setuid for instance).
As an example: the pwsafe app suggest you have to run it suid (since it
tries to lock some memory to avoid swapping), but doing 'setcap
cap_ipc_lock=ep /usr/bin/pwsafe' is enough.
> The step right afterward would be, for me, to find a way to mirror the
> capabilities from within Portage. I admit I have no clue how to achieve
> that for now. But at least the rename is a simple task, and I suppose
> the capabilities handling _could_ be a SoC project...
Well, I'm not sure whether libcap is a good choice: What about
(not-yet-existing) apps which provide capability-support through another
package (like a foobar language libcap-wrapper)? Should they also use
libcap then?
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-03-07 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 20:56 [gentoo-dev] [RFC] Renaming the caps USE flag to libcap Diego 'Flameeyes' Pettenò
2008-03-07 14:34 ` Tiziano Müller [this message]
2008-03-07 16:12 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
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='fqrjoq$eaq$1@ger.gmane.org' \
--to=dev-zero@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox