openssh bugs - Apr 2014 - [Bug 2219] New: Can't use -Ocancel on forward of dynamically allocated remote port

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

            Bug ID: 2219
           Summary: Can't use -Ocancel on forward of dynamically allocated
                    remote port
           Product: Portable OpenSSH
           Version: 6.5p1
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: quantheory at gmail.com

If you are using a multiplexed connection, you can request a
dynamically allocated remote port forward, but then there is no way to
cancel it afterward.

Example:
> ssh -Oforward -R 0:127.0.0.1:56789 user at remote
Allocated port 12345 for remote forward to 127.0.0.1:56789
12345
> ssh -Ocancel -R 0:127.0.0.1:56789 user at remote
mux_client_forward: forwarding request failed: port not in permitted
opens
muxclient: master cancel forward request failed
> ssh -Ocancel -R 12345:127.0.0.1:56789 user at remote
mux_client_forward: forwarding request failed: port not forwarded
muxclient: master cancel forward request failed

At least the second one should work, but OpenSSH doesn't check the
cancel request against the allocated port in this case.

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

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

Norman Rasmussen <norman at rasmussen.co.za> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |norman at rasmussen.co.za

--- Comment #1 from Norman Rasmussen <norman at rasmussen.co.za> ---
Works for me with 8.4p1, so I'm guessing it has been fixed since.

$ ssh -O forward -R 0:localhost:1234 remote
35077
$ ssh -O cancel -R 0:localhost:1234 remote
$

There was a fix "markus at cvs.openbsd.org 2011/09/23 07:45:05" that
looks
potentially relevant, except that it was committed way before 6.5p1.

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