diff options
| author | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-07-29 08:27:27 +0100 |
|---|---|---|
| committer | Szabolcs Nagy <szabolcs.nagy@arm.com> | 2020-08-03 22:37:23 +0100 |
| commit | 42c9e9af22dc645c06395879d36a565c6dc19f3a (patch) | |
| tree | f5541cdcb3df4ee8a3b758340f4540cc0673caf6 | |
| parent | 17a0126abf02955cabf6256c67f8f9462a64163f (diff) | |
| download | glibc-42c9e9af22dc645c06395879d36a565c6dc19f3a.zip glibc-42c9e9af22dc645c06395879d36a565c6dc19f3a.tar.gz glibc-42c9e9af22dc645c06395879d36a565c6dc19f3a.tar.bz2 | |
aarch64: update NEWS about branch protection
After some discussions it seems the original news was not clear
and that it is valid to manually pass the branch protection flags
iff GCC target libs are built with them too. The main difference
between manually passing the flags and using the configure
option is that the latter also makes branch protection the
default in GCC which may not be desirable in some cases.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
| -rw-r--r-- | NEWS | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -70,7 +70,9 @@ Major new features: * AArch64 now supports standard branch protection security hardening in glibc when it is built with a GCC that is configured with - --enable-standard-branch-protection. This includes branch target + --enable-standard-branch-protection (or if -mbranch-protection=standard + flag is passed when building both GCC target libraries and glibc, + in either case a custom GCC is needed). This includes branch target identification (BTI) and pointer authentication for return addresses (PAC-RET). They require armv8.5-a and armv8.3-a architecture extensions respectively for the protection to be effective, |