public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
* Question regarding file capabilities being shipped in Core Updates
@ 2021-07-07 18:26 Peter Müller
  2021-07-07 19:51 ` Adolf Belka
  2021-07-14 16:54 ` Michael Tremer
  0 siblings, 2 replies; 3+ messages in thread
From: Peter Müller @ 2021-07-07 18:26 UTC (permalink / raw)
  To: development

[-- Attachment #1: Type: text/plain, Size: 306 bytes --]

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question regarding file capabilities being shipped in Core Updates
  2021-07-07 18:26 Question regarding file capabilities being shipped in Core Updates Peter Müller
@ 2021-07-07 19:51 ` Adolf Belka
  2021-07-14 16:54 ` Michael Tremer
  1 sibling, 0 replies; 3+ messages in thread
From: Adolf Belka @ 2021-07-07 19:51 UTC (permalink / raw)
  To: development

[-- Attachment #1: Type: text/plain, Size: 861 bytes --]

Hi Peter,

In the CHANGES file in the source tarball setcap is mentioned twice:-

===== s20200821 =====
released August 21, 2020

* arping
- [security] disable setcap and setuid (prevent ARP Poisoning, issue: #203)

* Meson build system
- Allow to set using setcap-setuid.sh per application (commit: 054670a)

The setcap-setuid.sh script is in the build-aux directory in the source tarball. Maybe this script is what needs to be used now.

Hope this helps.

Regards,

Adolf.

On 07/07/2021 20:26, Peter Müller 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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Question regarding file capabilities being shipped in Core Updates
  2021-07-07 18:26 Question regarding file capabilities being shipped in Core Updates Peter Müller
  2021-07-07 19:51 ` Adolf Belka
@ 2021-07-14 16:54 ` Michael Tremer
  1 sibling, 0 replies; 3+ messages in thread
From: Michael Tremer @ 2021-07-14 16:54 UTC (permalink / raw)
  To: development

[-- 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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-07-14 16:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-07 18:26 Question regarding file capabilities being shipped in Core Updates Peter Müller
2021-07-07 19:51 ` Adolf Belka
2021-07-14 16:54 ` Michael Tremer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox