From: tavianator <tavianator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: bfs: update to 2.2.
Date: Tue, 23 Mar 2021 16:35:56 +0100 [thread overview]
Message-ID: <20210323153556.onCXaYf6OIxgaGSpbgJGX0RqYXRtxHkIhyVlpY7Stvk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29437@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
New comment by tavianator on void-packages repository
https://github.com/void-linux/void-packages/pull/29437#issuecomment-805003949
Comment:
Actually `setpriv` works fine, I just had the wrong ownership of `/` in my container. But I got `capsh` working too, thanks to this hint from the `setpriv` manpage:
```
If you drop a capability from the bounding set without
also dropping it from the inheritable set, you are likely
to become confused. Do not do that.
```
It seems like CAP_DAC_{OVERRIDE,READ_SEARCH} are inheritable in a container, so I have to remove them. Patch coming.
next prev parent reply other threads:[~2021-03-23 15:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 17:19 [PR PATCH] " daniel-eys
2021-03-13 17:30 ` daniel-eys
2021-03-22 14:38 ` tavianator
2021-03-22 20:35 ` [PR PATCH] [Updated] " daniel-eys
2021-03-22 20:42 ` daniel-eys
2021-03-22 21:03 ` tavianator
2021-03-22 21:26 ` tavianator
2021-03-22 21:49 ` [PR PATCH] [Updated] " daniel-eys
2021-03-22 22:11 ` ericonr
2021-03-23 15:08 ` tavianator
2021-03-23 15:35 ` tavianator [this message]
2021-03-23 15:49 ` tavianator
2021-04-03 4:19 ` ericonr
2021-04-03 9:25 ` [PR PATCH] [Updated] " daniel-eys
2021-04-03 9:26 ` daniel-eys
2021-04-03 13:12 ` [PR PATCH] [Merged]: " ericonr
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=20210323153556.onCXaYf6OIxgaGSpbgJGX0RqYXRtxHkIhyVlpY7Stvk@z \
--to=tavianator@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).