From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Boris Ouretskey <borisusun@gmail.com>
Cc: users@dpdk.org
Subject: Re: Issue setting up the DPDK development with non-privileged user
Date: Fri, 2 Sep 2022 17:31:54 +0300 [thread overview]
Message-ID: <20220902173154.57f5210c@sovereign> (raw)
In-Reply-To: <20220901222612.542840fe@sovereign>
2022-09-01 22:26 (UTC+0300), Dmitry Kozlyuk:
> 2022-09-01 17:42 (UTC+0300), Dmitry Kozlyuk:
> > Theoretically, one can enumerate all capabilities, give all capabilities
> > except one to the binary, try to run it, and notice which capability removal
> > leads to a failure. However, `setcap "all=ep $capa-ep" ./binary`
> > did not give the correct answer to me (why?), so I did it semi-manually.
>
> Aha! CAP_DAC_OVERRIDE and CAP_DAC_READ_SEARCH are not orthogonal:
> they both allow bypassing file read permission check.
>
> I have a working script here: ...
Apparently, a better alternative is already out there:
https://github.com/iovisor/bcc/blob/master/tools/capable_example.txt
next prev parent reply other threads:[~2022-09-02 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 14:10 Boris Ouretskey
2022-08-31 16:01 ` Dmitry Kozlyuk
2022-09-01 12:52 ` Boris Ouretskey
2022-09-01 14:42 ` Dmitry Kozlyuk
2022-09-01 19:26 ` Dmitry Kozlyuk
2022-09-02 14:31 ` Dmitry Kozlyuk [this message]
2022-09-03 18:18 ` Boris Ouretskey
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=20220902173154.57f5210c@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=borisusun@gmail.com \
--cc=users@dpdk.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).