From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding file capabilities being shipped in Core Updates
Date: Wed, 14 Jul 2021 17:54:28 +0100 [thread overview]
Message-ID: <3439DE3B-6F42-411A-A9B8-D65EE7162CF0@ipfire.org> (raw)
In-Reply-To: <3ada475f-2260-9e65-b044-b9034b72d4ba@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
For completeness. This has been fixed in:
https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=37ef9fe4e07a97d3597b9d9e7895652fcfe79150
The capabilities where set correctly, but strip removed them later and so nothing landed in the ISO or updater.
Best,
-Michael
> On 7 Jul 2021, at 19:26, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello *,
>
> while working on bug #12652, I noticed we _did_ ship ping / iputils in Core Update 157. However,
> it seems as the capabilities set to /usr/bin/ping are not preserved that way.
>
> Am I mistaken? Can we even use file capabilities in this environment?
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2021-07-14 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 18:26 Peter Müller
2021-07-07 19:51 ` Adolf Belka
2021-07-14 16:54 ` Michael Tremer [this message]
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=3439DE3B-6F42-411A-A9B8-D65EE7162CF0@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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