From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: fcaps.eclass: bringing filesystem capabilities to the tree
Date: Sat, 26 Jan 2013 10:17:16 +0000 (UTC) [thread overview]
Message-ID: <pan.2013.01.26.10.17.18@cox.net> (raw)
In-Reply-To: 201301260246.12861.vapier@gentoo.org
Mike Frysinger posted on Sat, 26 Jan 2013 02:46:12 -0500 as excerpted:
> if the package supports USE=caps, then it means the program is
> intelligent enough to know what capabilities it needs and so it can drop
> all of the rest before executing the main body of code.
> wouldn't it be nice if you could set the required capabilities on a
> binary and drop the set*id entirely ? that's what USE=filecaps gets us.
Very useful summary. Thanks. =:^)
I had all the pieces from various reading, but they were more in a heap
than assembled, and just the other day I was trying to assemble them into
something coherent (triggered by this thread, IIRC), but discovered I
still needed a bit of help. This was exactly what I needed for the
accumulated information to all fall into place! Thanks again! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2013-01-26 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 23:51 [gentoo-dev] fcaps.eclass: bringing filesystem capabilities to the tree Mike Frysinger
2013-01-26 0:10 ` Gilles Dartiguelongue
2013-01-26 0:17 ` Diego Elio Pettenò
2013-01-26 7:46 ` Mike Frysinger
2013-01-26 10:17 ` Duncan [this message]
2013-01-26 16:01 ` Diego Elio Pettenò
2013-01-26 16:13 ` Rich Freeman
2013-01-26 17:02 ` Diego Elio Pettenò
2013-01-28 19:58 ` Gilles Dartiguelongue
2013-01-26 13:21 ` Michał Górny
2013-01-26 17:08 ` Mike Frysinger
2013-01-26 21:07 ` Doug Goldstein
2013-01-27 17:26 ` Mike Frysinger
2013-01-27 18:24 ` Kacper Kowalik
2013-01-29 12:14 ` [gentoo-dev] " Duncan
2013-01-30 0:47 ` Diego Elio 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=pan.2013.01.26.10.17.18@cox.net \
--to=1i5t5.duncan@cox.net \
--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