From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re-shipping binaries due to _FORTIFY_SOURCE=3
Date: Tue, 21 May 2024 09:50:00 +0000
Message-ID: <72272574-b5a9-4c86-a9de-dc6f16a0e3b0@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5925867738264942365=="
List-Id: <development.lists.ipfire.org>

--===============5925867738264942365==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello *,

while trying to figure out the odd Suricata and kernel behavior with Core Upd=
ate 186
I encountered the other day, I noted that cecad543cb59d0e052cea437cc064bb0924=
cdbd2
mentions that having properly applied the  _FORTIFY_SOURCE=3D3 change entails=
 that we
re-ship "everything" (I assume that means every executable binary :-) ).

It seems like we didn't do so ever since this commit was merged into next, an=
d while
doing so in one go is not possible, I was wondering if we perhaps want to re-=
ship
the most critical parts, such as binaries of services directly exposed to the=
 network,
the glibc, and similar components.

Just a thought that occurred to me.

Thanks, and best regards,
Peter M=C3=BCller

--===============5925867738264942365==--