public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Joe Simmons-Talbott <josimmon@redhat.com>, libc-alpha@sourceware.org
Cc: Joe Talbott <joetalbott@gmail.com>
Subject: Re: [PATCH] manual/tunables - Add entry for enable_secure tunable.
Date: Fri, 1 Mar 2024 10:21:33 -0500	[thread overview]
Message-ID: <469de7f1-19a1-44e6-aacb-09cb11fc2006@gotplt.org> (raw)
In-Reply-To: <20240229212050.547864-1-josimmon@redhat.com>



On 2024-02-29 16:20, Joe Simmons-Talbott wrote:
> From: Joe Talbott <joetalbott@gmail.com>
> 
> ---

OK with a small nit fix below.  Please fix that and push, also posting 
the updated patch as [committed] to the mailing list.

Thanks,
Sid

Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>

>   manual/tunables.texi | 10 ++++++++++
>   1 file changed, 10 insertions(+)
> 
> diff --git a/manual/tunables.texi b/manual/tunables.texi
> index be97190d67..280d90dd5d 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
> +enable_secure.  Setting this tunable to @samp{1} also disables all other

@code{enable_secure}

> +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

  reply	other threads:[~2024-03-01 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 21:20 Joe Simmons-Talbott
2024-03-01 15:21 ` Siddhesh Poyarekar [this message]
2024-03-01 17:46 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=469de7f1-19a1-44e6-aacb-09cb11fc2006@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=joetalbott@gmail.com \
    --cc=josimmon@redhat.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).