From: Joe Simmons-Talbott <josimmon@redhat.com>
To: libc-alpha@sourceware.org
Cc: Joe Talbott <joetalbott@gmail.com>
Subject: [PATCH] NEWS: Move enable_secure_tunable from 2.39 to 2.40.
Date: Thu, 29 Feb 2024 16:46:44 -0500 [thread overview]
Message-ID: <20240229214654.2306477-1-josimmon@redhat.com> (raw)
From: Joe Talbott <joetalbott@gmail.com>
---
NEWS | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/NEWS b/NEWS
index 19f4e93ea3..da4b2223e9 100644
--- a/NEWS
+++ b/NEWS
@@ -21,6 +21,11 @@ Major new features:
by _GNU_SOURCE, or by compiling with the GCC options -std=c23,
-std=gnu23, -std=c2x or -std=gnu2x.
+* A new tunable, glibc.rtld.enable_secure, used to run a program
+ as if it were a setuid process. This is currently a testing tool to allow
+ more extensive verification tests for AT_SECURE programs and not meant to
+ be a security feature.
+
Deprecated and removed features, and other changes affecting compatibility:
[Add deprecations, removals and changes affecting compatibility here]
@@ -103,11 +108,6 @@ Major new features:
exp, expf, exp10, exp10f, exp2, exp2f, expm1, expm1f, log, logf,
log10, log10f, log1p, log1pf, log2, log2f, sin, sinf, tan, tanf.
-* A new tunable, glibc.rtld.enable_secure, used to run a program
- as if it were a setuid process. This is currently a testing tool to allow
- more extensive verification tests for AT_SECURE programs and not meant to
- be a security feature.
-
Deprecated and removed features, and other changes affecting compatibility:
* The ldconfig program now skips file names containing ';' or ending in
--
2.43.2
next reply other threads:[~2024-02-29 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 21:46 Joe Simmons-Talbott [this message]
2024-03-01 15:18 ` Siddhesh Poyarekar
2024-03-01 17:39 ` Joe Simmons-Talbott
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=20240229214654.2306477-1-josimmon@redhat.com \
--to=josimmon@redhat.com \
--cc=joetalbott@gmail.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).