https://bugzilla.mindrot.org/show_bug.cgi?id=3017
--- Comment #8 from Wiebe Cazemier ---
What exactly is the lack of follow-up? I thought the cause was clear?
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
Damien Miller changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
Darren Tucker changed:
What|Removed |Added
CC||dtuc...@dtucker.net
--- Comment #6 from
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
--- Comment #5 from Pavel Sidlo ---
I've faced probably the same behavior for RemoteForward.
I seems sshd by default allocates both tcp and tcp6 sockets.
ExitOnForwardFailure fails to reject connection if tcp is already in
use but tcp6 is not
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
Pavel Sidlo changed:
What|Removed |Added
CC||pavel.si...@linuxbox.cz
--
You are
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
--- Comment #4 from Wiebe Cazemier ---
Created attachment 3435
--> https://bugzilla.mindrot.org/attachment.cgi?id=3435=edit
ssh -vvv output
Debug trace with ExitOnForwardFailure=yes that still logs in.
--
You are receiving this mail because:
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
Damien Miller changed:
What|Removed |Added
CC||d...@mindrot.org
--- Comment #3 from
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
--- Comment #2 from Wiebe Cazemier ---
Another interesting result: it started happening randomly. Apparently,
it switched between ipv4 and ipv6. With -4, it works properly and fails
consistently.
--
You are receiving this mail because:
You are
https://bugzilla.mindrot.org/show_bug.cgi?id=3017
--- Comment #1 from Wiebe Cazemier ---
It does work properly from Ubuntu 16.04, Openssh 7.2p2-4ubuntu2.8:
ssh -L 22022:localhost:22 -o ExitOnForwardFailure=yes r...@server.com
-p 22022
bind: Address already in use
