[Bug 2200] New: ssh -W causes "getsockname failed: Bad file descriptor" errors

[bugzilla-daemon at mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=2200

            Bug ID: 2200
           Summary: ssh -W causes "getsockname failed: Bad file
                    descriptor" errors
           Product: Portable OpenSSH
           Version: 6.5p1
          Hardware: All
               URL: http://bugs.debian.org/738693
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: cjwatson at debian.org

Marco d'Itri reports in http://bugs.debian.org/738693 that "ssh -W" has
started causing "getsockname failed: Bad file descriptor" errors; these
are new in 6.5p1 and reported via error().  I think this was triggered
by the new calls to get_sock_port from port_open_helper in
https://anongit.mindrot.org/openssh.git/commit/?id=4def184; gdb shows
that c->sock is -1 here.

Full -vvv output in the Debian bug; relevant-looking excerpt:

debug3: ssh_init_stdio_forwarding: server2.example.net:22
debug1: channel_connect_stdio_fwd server2.example.net:22
debug1: channel 0: new [stdio-forward]
debug2: fd 4 setting O_NONBLOCK
debug3: fd 5 is O_NONBLOCK
getsockname failed: Bad file descriptor
debug1: getpeername failed: Bad file descriptor

It looks like it still works fine, but the extra non-debug error is
annoying.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.