public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <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	[thread overview]
Message-ID: <72272574-b5a9-4c86-a9de-dc6f16a0e3b0@ipfire.org> (raw)

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

Hello *,

while trying to figure out the odd Suricata and kernel behavior with Core Update 186
I encountered the other day, I noted that cecad543cb59d0e052cea437cc064bb0924cdbd2
mentions that having properly applied the  _FORTIFY_SOURCE=3 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, and 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üller

             reply	other threads:[~2024-05-21  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  9:50 Peter Müller [this message]
2024-05-21 14:55 ` Michael Tremer

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=72272574-b5a9-4c86-a9de-dc6f16a0e3b0@ipfire.org \
    --to=peter.mueller@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