Bug 1103 - New option for ssh(1) to make it failing when remote port forwarding can't be established
Summary: New option for ssh(1) to make it failing when remote port forwarding can't be...
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: ssh (show other bugs)
Version: 3.8.1p1
Hardware: All All
: P2 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks: V_4_4
  Show dependency tree / graph
 
Reported: 2005-10-14 01:14 AEST by Maxim Sobolev
Modified: 2006-09-28 19:25 AEST (History)
0 users

See Also:

Attachments
Proposed patch. (3.28 KB, patch)
2005-10-14 01:16 AEST, Maxim Sobolev 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maxim Sobolev 2005-10-14 01:14:45 AEST 
Hi,

In some cases it's necessary to ensure that remote port forwarding has been established properly. Unfortunately it's impossible to do in the current ssh since failure to establish forwarding is not fatal. Attached please find patch which adds new option for ssh (default is off), which allows to make such condition a fatal error, resulting in ssh(1) exiting with error code when one of requested remote forwardings can't be established for some reason.

-Maxim
Comment 1 Maxim Sobolev 2005-10-14 01:16:08 AEST 
Created attachment 995 [details]
Proposed patch.
Comment 2 Damien Miller 2006-07-12 07:45:34 AEST 
openssh-4.4 supports an ExitOnForwardFailure option that does this
Comment 3 Darren Tucker 2006-09-28 19:25:37 AEST 
With the release of 4.4, we believe that this bug is now closed.  For information about the release please see http://www.openssh.com/txt/release-4.4 .