All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iputils: set the permissions with IPUTILS_PERMISSIONS
Date: Wed, 19 Jun 2019 07:01:29 +0200	[thread overview]
Message-ID: <20190619050127.GA21810@dell5510> (raw)
In-Reply-To: <4da3ae28-a8f3-7f49-0583-083b5ea15f75@mind.be>

Hi Arnout,

> >>  > It'd be nice if buildroot has BR2_TARGET_ROOTFS_HAS_XATTRS.

> >> The problem is that you can enable several rootfs formats at the same
> >> time (E.G. tar and cramfs), so we would need to only use xattrs if no
> >> file system without xattrs support is enabled.

>  So maybe we could add a system option BR2_SYSTEM_XATTR that enables the use of
> xattr.
+1

>  Currently we have nothing using xattr, but there are quite a few packages that
> could benefit from it, e.g. libpcap, and SELinux stuff.
And IMA+EVM kernel features.

>  We could use that option to enable xattr instead of setuid where relevant, and
> to disable filesystems that don't support xattr.


> >> And things would break if you do a build with E.G. only tar rootfs
> >> support and then afterwards enable cramfs without doing a clean
> >> rebuild - Yes, I know you are not supposed to do that, but it does
> >> happen.

>  I don't think we need to worry about that. But actually, with the
> BR2_SYSTEM_XATTR option, it would even work since it's only taken into account
> during finalize.


> > Thanks for detailed info. I guess in that case is setuid really the only option.

>  It isn't, but the alternatives are a lot of work :-)
:-). Do you plan to work on it? If not, I might do in next few weeks (I'm quite
busy during summer).

>  Regards,
>  Arnout

Kind regards,
Petr

  reply	other threads:[~2019-06-19  5:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 23:07 [Buildroot] [PATCH 1/1] iputils: set the permissions with IPUTILS_PERMISSIONS Petr Vorel
2019-06-10 13:45 ` Arnout Vandecappelle
2019-06-10 20:06   ` Petr Vorel
2019-06-10 21:26     ` Arnout Vandecappelle
2019-06-13 19:37       ` Peter Korsgaard
2019-06-14 16:24         ` Petr Vorel
2019-06-18 12:45           ` Peter Korsgaard
2019-06-18 20:52             ` Petr Vorel
2019-06-18 21:31               ` Arnout Vandecappelle
2019-06-19  5:01                 ` Petr Vorel [this message]
2019-06-19  6:50                   ` Arnout Vandecappelle
2019-06-19  6:52                     ` Petr Vorel
2019-06-19  7:11                     ` Peter Korsgaard

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=20190619050127.GA21810@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 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.