[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[fweimer at redhat dot com]

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com
         Resolution|WONTFIX                     |DUPLICATE
              Flags|                            |security-

--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
Fixed.

*** This bug has been marked as a duplicate of bug 1451 ***

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

[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[fweimer at redhat dot com]

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

--- Comment #5 from Florian Weimer <fweimer at redhat dot com> ---


*** This bug has been marked as a duplicate of bug 14516 ***

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

[Bug libc/3353] New: ttyname's new strict dependency on /proc breaks chrooted applications

[jnair at ensim dot com]

I am a FC6(test3) user. glibc version comes with the distro is 2.4.90-29.
My application runs sshd daemon and logons users to their respective chrooted
homes. Now /proc is not purposely made available in the chrooted env. 
sshd's login process (chrooted) calls ttyname. It fails as it does not find
/proc mounted. This used to work with glibc-2.4-4 (on FC5) and before.
Now this strict dependency breaks my application. Even simple command like `tty`
fails in if /proc is not mounted.

-- 
           Summary: ttyname's new strict dependency on /proc breaks chrooted
                    applications
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: critical
          Priority: P1
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: jnair at ensim dot com
                CC: glibc-bugs at sources dot redhat dot com,shekhar dot
                    tiwatne at ensim dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=3353

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[drepper at redhat dot com]

------- Additional Comments From drepper at redhat dot com  2006-10-12 20:57 -------
glibc cannot work reliably at all without /proc.  This is (unfortunately) the
only interface to all kinds of kernel details.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX


http://sourceware.org/bugzilla/show_bug.cgi?id=3353

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[jakub at redhat dot com]

------- Additional Comments From jakub at redhat dot com  2006-10-12 21:04 -------
BTW, if you for whatever reason don't want to mount whole /proc into the chroots,
you can always at least mount --bind there parts of it sufficient enough
to make all programs you want to run in the chroot happy.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3353

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/3353] ttyname's new strict dependency on /proc breaks chrooted applications

[jnair at ensim dot com]

------- Additional Comments From jnair at ensim dot com  2006-10-13 05:30 -------
(In reply to comment #2)
> BTW, if you for whatever reason don't want to mount whole /proc into the chroots,
> you can always at least mount --bind there parts of it sufficient enough
> to make all programs you want to run in the chroot happy.


I agree but, 'ttyname' i belive does a 'readlink'  on '/proc/self/fd/n' and
'self' will be known only to the forked 'sshd' child,so binding 'part' of the
proc fs in this case is not possible. Hope i got it right.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3353

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.