OpenSSF gold badge: apply hardening fixes from #1241 without enabling hardening itself#1348
Conversation
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
figueroa1395
left a comment
There was a problem hiding this comment.
Can you rename the PR? We already have the silver badge, perhaps we can name name this one gold badge, since this is needed for that milestone.
Besides this, no more comments from me. LGTM.
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
|
|
Hi @mgovers, @figueroa1395, I took out this PR out of merge queue because I still have some questions. We have indeed some decisions to make about whether and how enable hardening build flags for release distribution. But we can enable harnding flags in development cmake presets right?. That should check in the CI? |
I think so, but i'd consider that a follow-up. #1241 has been open for so long that the fixes (which are actual cases of UB) should not be delayed any longer. IMO, we should scope out the other choices to a separate PR (maybe we can decide on the exact form on thursday) |



Relates to #1241 .
In #1241 , a number of fixes were applied. This PR cherry-picks those fixes without actually enabling hardening itself. This enables safer code without enforcing things that are still TBD.