Bug 2033683
Summary: | Enable _FORTIFY_SOURCE=3 for gcc 12 and later [9.1.0] | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Siddhesh Poyarekar <sipoyare> | |
Component: | glibc | Assignee: | Florian Weimer <fweimer> | |
Status: | CLOSED ERRATA | QA Contact: | Sergey Kolosov <skolosov> | |
Severity: | unspecified | Docs Contact: | Jacob Taylor Valdez <jvaldez> | |
Priority: | unspecified | |||
Version: | 9.0 | CC: | ashankar, codonell, dj, fweimer, jvaldez, mnewsome, pfrankli, sipoyare, skolosov | |
Target Milestone: | rc | Keywords: | FutureFeature, Patch, Triaged | |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
|
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glibc-2.34-29.el9 | Doc Type: | Enhancement | |
Doc Text: |
.GCC 12 and later supports `_FORTIFY_SOURCE` level 3
With this enhancement, users can build applications with `-D_FORTIFY_SOURCE=3` in the compiler command line when building with GCC version 12 or later. `_FORTIFY_SOURCE` level 3 improves coverage of source code fortification, thus improving security for applications built with `-D_FORTIFY_SOURCE=3` in the compiler command line. This is supported in GCC versions 12 and later and all Clang in RHEL 9 with the `__builtin_dynamic_object_size` builtin.
|
Story Points: | --- | |
Clone Of: | ||||
: | 2033684 (view as bug list) | Environment: | ||
Last Closed: | 2022-11-15 11:11:43 UTC | Type: | Enhancement | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 2063230 | |||
Bug Blocks: |
Description
Siddhesh Poyarekar
2021-12-17 15:50:36 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glibc bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8272 |