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: Tue, 30 Jul 2019 23:38:46 +0200 [thread overview]
Message-ID: <20190730213846.7488-2-petr.vorel@gmail.com> (raw)
In-Reply-To: <20190730213846.7488-1-petr.vorel@gmail.com>
Not setting for arping as it can be used for ARP Poisoning.
Use cap_net_raw+p (drop +e) as upstream sets that via
cap_set_flag(), see https://github.com/iputils/iputils/issues/194
Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
---
package/iputils/iputils.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/iputils/iputils.mk b/package/iputils/iputils.mk
index 8e6a3e2fc5..f1d3e1fc6a 100644
--- a/package/iputils/iputils.mk
+++ b/package/iputils/iputils.mk
@@ -76,8 +76,11 @@ IPUTILS_CONF_OPTS += -DNO_SETCAP_OR_SUID=true
define IPUTILS_PERMISSIONS
/usr/sbin/arping f 4755 0 0 - - - - -
/usr/bin/clockdiff f 4755 0 0 - - - - -
+ |xattr cap_net_raw+p
/bin/ping f 4755 0 0 - - - - -
+ |xattr cap_net_raw+p
/usr/bin/traceroute6 f 4755 0 0 - - - - -
+ |xattr cap_net_raw+p
endef
$(eval $(meson-package))
--
2.22.0
next prev parent reply other threads:[~2019-07-30 21:38 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 ` Petr Vorel [this message]
2019-07-31 16:00 ` [Buildroot] [RFC PATCH v4 2/2] iputils: add capability for clockdiff, ping, traceroute6 Yann E. MORIN
2019-07-31 20:11 ` Petr Vorel
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=20190730213846.7488-2-petr.vorel@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.