public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/nsz/pacbti-v7] aarch64: add NEWS entry about branch protection support Date: Wed, 8 Jul 2020 12:09:43 +0000 (GMT) [thread overview] Message-ID: <20200708120943.8DEBB386188D@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=90d6dfb05675c96e1f4cd35187d2fb783fc00204 commit 90d6dfb05675c96e1f4cd35187d2fb783fc00204 Author: Szabolcs Nagy <szabolcs.nagy@arm.com> Date: Thu Jun 11 18:19:40 2020 +0100 aarch64: add NEWS entry about branch protection support This is a new security feature that relies on architecture extensions and needs glibc to be built with a gcc configured with branch protection. Diff: --- NEWS | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/NEWS b/NEWS index d7282b4ad5..5083f5eacf 100644 --- a/NEWS +++ b/NEWS @@ -67,6 +67,17 @@ Major new features: They should be used instead of sys_errlist and sys_nerr, both are thread and async-signal safe. These functions are GNU extensions. +* 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. + Deprecated and removed features, and other changes affecting compatibility: * The deprecated <sys/sysctl.h> header and the sysctl function have been
reply other threads:[~2020-07-08 12:09 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200708120943.8DEBB386188D@sourceware.org \ --to=nsz@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).