From: Joe Simmons-Talbott <josimmon@redhat.com>
To: libc-alpha@sourceware.org
Cc: Joe Talbott <joetalbott@gmail.com>
Subject: Re: [committed] manual/tunables - Add entry for enable_secure tunable.
Date: Fri, 1 Mar 2024 12:47:33 -0500 [thread overview]
Message-ID: <CAAQBMsP7LkNALnpvBB91+m=Tc9XTi2_EVSFEob1EJG=qBcCvZg@mail.gmail.com> (raw)
In-Reply-To: <20240301174659.2012703-1-josimmon@redhat.com>
I neglected to change the subject line. Please disregard.
Thanks,
Joe
On Fri, Mar 1, 2024 at 12:47 PM Joe Simmons-Talbott <josimmon@redhat.com> wrote:
>
> From: Joe Talbott <joetalbott@gmail.com>
>
> ---
> manual/tunables.texi | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/manual/tunables.texi b/manual/tunables.texi
> index be97190d67..4a7d04dc0d 100644
> --- a/manual/tunables.texi
> +++ b/manual/tunables.texi
> @@ -345,6 +345,16 @@ performance issues of @samp{1}.
> The default value of this tunable is @samp{2}.
> @end deftp
>
> +@deftp Tunable glibc.rtld.enable_secure
> +Used to run a program as if it were a setuid process. The only valid value
> +is @samp{1} as this tunable can only be used to set and not unset
> +@code{enable_secure}. Setting this tunable to @samp{1} also disables all other
> +tunables. This tunable is intended to facilitate more extensive verification
> +tests for @code{AT_SECURE} programs and not meant to be a security feature.
> +
> +The default value of this tunable is @samp{0}.
> +@end deftp
> +
> @node Elision Tunables
> @section Elision Tunables
> @cindex elision tunables
> --
> 2.43.2
>
--
Joe Simmons-Talbott
prev parent reply other threads:[~2024-03-01 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 17:46 Joe Simmons-Talbott
2024-03-01 17:47 ` Joe Simmons-Talbott [this message]
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='CAAQBMsP7LkNALnpvBB91+m=Tc9XTi2_EVSFEob1EJG=qBcCvZg@mail.gmail.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).