You are not logged in.

#1 2014-03-16 04:36:41

sylvite
Member
Registered: 2014-03-16
Posts: 16

ssh -W causes "getsockname failed: Bad file descriptor" errors

Using openssh 6.5p1-2, this error(?) message occurs frequently
    getsockname failed: Bad file descriptor

This has been reported to debian and mindrot:
    https://bugzilla.mindrot.org/show_bug.cgi?id=2200
    https://bugs.debian.org/cgi-bin/bugrepo … bug=738693
and has been fixed:
    https://bugzilla.mindrot.org/attachment.cgi?id=2407

Can this patch be applied to the official arch openssh package?

Offline

#2 2014-03-16 04:47:58

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: ssh -W causes "getsockname failed: Bad file descriptor" errors

Have a look on the Arch bugtracker and see if it has been logged. If it hasn't, and hasn't been accepted upstream, you could open a report there: it's more likely a developer will see it there...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2014-03-19 01:16:12

sylvite
Member
Registered: 2014-03-16
Posts: 16

Re: ssh -W causes "getsockname failed: Bad file descriptor" errors

This appears to be fixed with latest openssh 6.6p1-1.

Offline

Board footer

Powered by FluxBB