public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: "Cristian Rodríguez" <crrodriguez@opensuse.org>,
	"Adhemerval Zanella Netto" <adhemerval.zanella@linaro.org>
Cc: Sergey Bugaev <bugaevc@gmail.com>,
	libc-alpha@sourceware.org, bug-hurd <bug-hurd@gnu.org>,
	Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: [RFC PATCH v2 4/7] csu: Fix standard fds' mode
Date: Fri, 21 Apr 2023 10:16:40 -0700	[thread overview]
Message-ID: <3fc6b5ea-76ed-ddf0-4e2f-a9975fdbe6f0@cs.ucla.edu> (raw)
In-Reply-To: <CAPBLoAcbrL=-rzqWXhM14K-cwqL7e-51AR6EU3gfMx+vqDfehA@mail.gmail.com>

On 2023-04-20 05:06, Cristian Rodríguez via Libc-alpha wrote:
> Exactly, my understanding is that it is a futile exercise ..if one
> sufficient privilege at that stage one can do whatever is desired..  why
> even bother messing with the standard fds..

Making stdin unreadable is not meant to thwart a root-privileged 
attacker. As the comment in check_one_fd says, it's merely meant to 
catch bugs in programs that accidentally (for example) read from 
standard input even though there is no standard input. If standard input 
is /dev/null and readable, these buggy programs silently behave as if 
the input is the empty file, which is likely incorrect. In contrast, if 
standard input is not readable, these buggy programs will get a read 
error, which is more likely to cause them to report an error and alert 
users of the bug.

So let's leave glibc/csu/check_fds.c alone: it serves a useful purpose.

PS. Sorry if this email is duplicate; I had mail server problems.

  parent reply	other threads:[~2023-04-21 17:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 16:02 [RFC PATCH v2 0/7] O_IGNORE_CTTY everywhere & misc fixes Sergey Bugaev
2023-04-19 16:02 ` [RFC PATCH v2 1/7] misc: Convert daemon () to GNU coding style Sergey Bugaev
2023-04-21 12:18   ` Adhemerval Zanella Netto
2023-04-22 11:47     ` Samuel Thibault
2023-04-19 16:02 ` [RFC PATCH v2 2/7] misc: Ignore SIGHUP in daemon () while forking Sergey Bugaev
2023-04-21 12:55   ` Adhemerval Zanella Netto
2023-04-19 16:02 ` [RFC PATCH v2 3/7] Use O_CLOEXEC in more places (BZ #15722) Sergey Bugaev
2023-04-21 12:55   ` Adhemerval Zanella Netto
2023-04-22 11:50     ` Samuel Thibault
2023-04-19 16:02 ` [RFC PATCH v2 4/7] csu: Fix standard fds' mode Sergey Bugaev
2023-04-19 19:13   ` Cristian Rodríguez
2023-04-19 19:40     ` Sergey Bugaev
2023-04-19 20:45       ` Adhemerval Zanella Netto
2023-04-19 21:16         ` Sergey Bugaev
2023-04-20 11:47           ` Adhemerval Zanella Netto
2023-04-20 12:06             ` Cristian Rodríguez
2023-04-20 15:13               ` Adhemerval Zanella Netto
2023-04-21 17:16               ` Paul Eggert [this message]
2023-04-19 16:02 ` [RFC PATCH v2 5/7] hurd: Make dl-sysdep's open () cope with O_IGNORE_CTTY Sergey Bugaev
2023-04-20 21:06   ` Samuel Thibault
2023-04-19 16:02 ` [RFC PATCH v2 6/7] include/fcntl.h: Define O_IGNORE_CTTY Sergey Bugaev
2023-04-19 16:02 ` [RFC PATCH v2 7/7] Use O_IGNORE_CTTY where appropriate Sergey Bugaev

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=3fc6b5ea-76ed-ddf0-4e2f-a9975fdbe6f0@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=adhemerval.zanella@linaro.org \
    --cc=bug-hurd@gnu.org \
    --cc=bugaevc@gmail.com \
    --cc=crrodriguez@opensuse.org \
    --cc=libc-alpha@sourceware.org \
    --cc=samuel.thibault@gnu.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).