From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v4 2/2] iputils: add capability for clockdiff, ping, traceroute6
Date: Wed, 31 Jul 2019 22:11:17 +0200 [thread overview]
Message-ID: <20190731201116.GD10819@dell5510> (raw)
In-Reply-To: <20190731160059.GJ3194@scaer>
Hi Yann,
> So, now we set the capabilities to those exectuables, do they still need
> to be setuid?
> But then, if one really does not want xattr, setuid is still required.
> So, we have no way to express that a file should have either setuid or
> xattrs, except as a big if-block like:
> ifeq ($(BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES),y)
> define IPUTILS_PERMISSIONS
> /usr/bin/clockdiff f 0755 0 0 - - - - -
> |xattr cap_net_raw+p
> endef
> else
> define IPUTILS_PERMISSIONS
> /usr/bin/clockdiff f 4755 0 0 - - - - -
> endef
> endif
> ... which is what we were trying to avoid in the firstplace...
> We could write something like:
> /usr/bin/clockdiff f $(MAYBE_SUID)755 0 0 - - - - -
> |xattr cap_net_raw+p
> Where MAYBE_SUID would be set as:
> MAYBE_SUID = $(if $(BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES),0,4)
Good point, I fixed it in v5 (with whitespace).
> But it is starting to be a bit more complex than what you initially
> envisionned, I guess.
Yep :(. But your solution is good enough, thank you!
Kind regards,
Petr
next prev parent reply other threads:[~2019-07-31 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 21:38 [Buildroot] [RFC PATCH v4 1/2] makedevs: only warn when xattr support disabled Petr Vorel
2019-07-30 21:38 ` [Buildroot] [RFC PATCH v4 2/2] iputils: add capability for clockdiff, ping, traceroute6 Petr Vorel
2019-07-31 16:00 ` Yann E. MORIN
2019-07-31 20:11 ` Petr Vorel [this message]
2019-07-31 22:13 ` Thomas Petazzoni
2019-07-31 22:24 ` Petr Vorel
2019-08-01 7:29 ` Yann E. MORIN
2019-08-01 7:33 ` Petr Vorel
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=20190731201116.GD10819@dell5510 \
--to=petr.vorel@gmail.com \
--cc=buildroot@busybox.net \
/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