Re-shipping binaries due to _FORTIFY_SOURCE=3

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