[Bug libc/27056] New: Incorrect access modes for stdin, stout and stderr in csu/check_fds.c

[Bug libc/27056] New: Incorrect access modes for stdin, stout and stderr in csu/check_fds.c

[dr.duncan.p.simpson at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27056

            Bug ID: 27056
           Summary: Incorrect access modes for stdin, stout and stderr in
                    csu/check_fds.c
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: dr.duncan.p.simpson at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

In check_fds.c I saw that stdin is opened as O_write only and stdout are stderr
are opened as read only, which is presumably less than ideal. Suggested fix

diff --git a/csu/check_fds.c b/csu/check_fds.c
index 29d9d04acb..5999d450a4 100644
--- a/csu/check_fds.c
+++ b/csu/check_fds.c
@@ -90,7 +90,7 @@ __libc_check_standard_fds (void)
      is really paranoid but some people actually are.  If /dev/null
      should happen to be a symlink to somewhere else and not the
      device commonly known as "/dev/null" we bail out.  */
-  check_one_fd (STDIN_FILENO, O_WRONLY | O_NOFOLLOW);
-  check_one_fd (STDOUT_FILENO, O_RDONLY | O_NOFOLLOW);
-  check_one_fd (STDERR_FILENO, O_RDONLY | O_NOFOLLOW);
+  check_one_fd (STDIN_FILENO, O_RDONLY | O_NOFOLLOW);
+  check_one_fd (STDOUT_FILENO, O_WRONLY | O_NOFOLLOW);
+  check_one_fd (STDERR_FILENO, O_WRONLY | O_NOFOLLOW);
 }

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/27056] Incorrect access modes for stdin, stout and stderr in csu/check_fds.c

[schwab@linux-m68k.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27056

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
This is by design.  If the program is started with 0/1/2 closed then access to
them should fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.