From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: libc-alpha@sourceware.org
Subject: [PATCH v6 14/14] aarch64: add NEWS entry about branch protection support
Date: Wed, 1 Jul 2020 15:41:11 +0100 [thread overview]
Message-ID: <62a4294111ba2d06fdc1772fee65960e1cc02e5d.1593612309.git.szabolcs.nagy@arm.com> (raw)
In-Reply-To: <cover.1593612309.git.szabolcs.nagy@arm.com>
This is a new security feature that relies on architecture
extensions and needs glibc to be built with a gcc configured
with branch protection.
---
NEWS | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/NEWS b/NEWS
index a660fc59a8..7d0ca3f520 100644
--- a/NEWS
+++ b/NEWS
@@ -31,6 +31,18 @@ Major new features:
pthread_attr_getsigmask_np have been added. They allow applications
to specify the signal mask of a thread created with pthread_create.
+* 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
+ 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,
+ otherwise the used instructions are nops. User code can use PAC-RET
+ without libc support, but BTI requires a libc that is built with BTI
+ support, otherwise runtime objects linked into user code will not be
+ BTI compatible. It is recommended to use GCC 10 or newer when
+ building glibc with branch protection.
+
Deprecated and removed features, and other changes affecting compatibility:
* The deprecated <sys/sysctl.h> header and the sysctl function have been
--
2.17.1
next prev parent reply other threads:[~2020-07-01 14:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 14:37 [PATCH v6 00/14] aarch64: " Szabolcs Nagy
2020-07-01 14:37 ` [PATCH v6 01/14] Rewrite abi-note.S in C Szabolcs Nagy
2020-07-01 14:41 ` H.J. Lu
2020-07-01 17:31 ` Szabolcs Nagy
2020-07-01 17:43 ` H.J. Lu
2020-07-02 8:39 ` Szabolcs Nagy
2020-07-01 14:38 ` [PATCH v6 02/14] aarch64: configure test for BTI support Szabolcs Nagy
2020-07-06 14:11 ` Adhemerval Zanella
2020-07-06 18:07 ` Szabolcs Nagy
2020-07-06 18:12 ` Adhemerval Zanella
2020-07-07 14:26 ` Szabolcs Nagy
2020-07-07 14:39 ` H.J. Lu
2020-07-07 16:58 ` Szabolcs Nagy
2020-07-07 17:24 ` H.J. Lu
2020-07-01 14:38 ` [PATCH v6 03/14] aarch64: Rename place holder .S files to .c Szabolcs Nagy
2020-07-01 14:38 ` [PATCH v6 04/14] aarch64: Add BTI support to assembly files Szabolcs Nagy
2020-07-03 16:19 ` Szabolcs Nagy
2020-07-01 14:38 ` [PATCH v6 05/14] aarch64: fix swapcontext for BTI Szabolcs Nagy
2020-07-01 14:39 ` [PATCH v6 06/14] aarch64: fix RTLD_START " Szabolcs Nagy
2020-07-01 14:39 ` [PATCH v6 07/14] rtld: Clean up PT_NOTE and add PT_GNU_PROPERTY handling Szabolcs Nagy
2020-07-06 16:11 ` Adhemerval Zanella
2020-07-01 14:39 ` [PATCH v6 08/14] aarch64: enable BTI at runtime Szabolcs Nagy
2020-07-06 17:28 ` Adhemerval Zanella
2020-07-11 15:58 ` Richard Henderson
2020-07-13 8:32 ` Szabolcs Nagy
2020-07-13 13:14 ` Szabolcs Nagy
2020-07-13 13:28 ` Szabolcs Nagy
2020-07-13 16:55 ` Richard Henderson
2020-07-01 14:39 ` [PATCH v6 09/14] aarch64: ensure objects are BTI compatible Szabolcs Nagy
2020-07-06 17:37 ` Adhemerval Zanella
2020-07-06 18:01 ` Szabolcs Nagy
2020-07-06 18:17 ` Adhemerval Zanella
2020-07-01 14:40 ` [PATCH v6 10/14] aarch64: configure check for pac-ret code generation Szabolcs Nagy
2020-07-01 14:40 ` [PATCH v6 11/14] aarch64: Add pac-ret support to assembly files Szabolcs Nagy
2020-07-01 14:40 ` [PATCH v6 12/14] aarch64: fix pac-ret support in _mcount Szabolcs Nagy
2020-07-06 18:33 ` Adhemerval Zanella
2020-07-01 14:40 ` [PATCH v6 13/14] aarch64: redefine RETURN_ADDRESS to strip PAC Szabolcs Nagy
2020-07-06 18:34 ` Adhemerval Zanella
2020-07-01 14:41 ` Szabolcs Nagy [this message]
2020-07-06 18:41 ` [PATCH v6 14/14] aarch64: add NEWS entry about branch protection support Adhemerval Zanella
2020-07-08 10:04 ` Szabolcs Nagy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62a4294111ba2d06fdc1772fee65960e1cc02e5d.1593612309.git.szabolcs.nagy@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).