#11173 Mass rebuild for _FORTIFY_SOURCE=3 in Fedora 38
Closed: Fixed a year ago by humaton. Opened a year ago by siddhesh.

  • Describe the issue
    I have proposed to change the default build flags for the distribution to add -Wp,-D_FORTIFY_SOURCE=3 to the default build flags to improve the default state of security in Fedora 38. The change will go into redhat-rpm-config and should be followed by a mass rebuild. We don't really need a separate mass rebuild, I could schedule the change so that it uses the planned rebuild on 18th Jan next year according to this schedule:

https://fedorapeople.org/groups/schedule/f-38/f-38-all-tasks.html

  • When do you need this? (YYYY/MM/DD)
    2023-01-18

  • When is this no longer needed or useful? (YYYY/MM/DD)
    2023-01-19

  • If we cannot complete your request, what is the impact?

Bugs in packages exposed by _FORTIFY_SOURCE=3 will not be exposed soon enough and may result in schedule slippage for Fedora 38.


Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

a year ago

Hi @siddhesh, thanks for contacting release engineering. I don't see your change approval by FESCO. Once that happens all that releng requires to include change into the scheduled mass rebuild is that the changes are in rawhide before 18.1 2023 at 14:00 UTC.

Metadata Update from @humaton:
- Issue tagged with: changes, f38, mass rebuild

a year ago

Thanks, I filed the ticket because I was asked to as a prerequisite to getting the proposal evaluated by FESCo. I'll drop a note when FESCo has voted on the proposal.

If you get all approvals, is it feasible to get changes in before the scheduled mass rebuild?

Mass rebuild is finished, closing.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog