Bug #145
SSH tunnel setup failed: Bad configuration option: ExitOnForwardFailure
| Status: | Closed | Start: | ||
| Priority: | High | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Frontend | |||
| Target version: | 0.6.4 | |||
| Complexity: | Found in Version: | |||
| Votes: | 0 |
Description
Looks like etch's openssh client doesn't support the ExitOnForwardFailure option. So either smuxi should not use it or check the openssh version first.
Associated revisions
Revision 9ac304d745ee5659e9ff50d34a6ba71ae1fe6de3
Only use the ExitOnForwardFailure option for the SSH tunnel if we are using OpenSSH >= 4.4p1. (closes: #145)
History
Updated by Mirco Bauer 5834 days ago
Used version on the frontend side:
ii openssh-client 4.3p2-9etch3 Secure shell client, an rlogin/rsh/rcp replaceme
On the internet I found this about the ExitOnForwardFailure option:
In earlier versions of OpenSSH, ssh does not terminate if port forwarding requests fail. Starting with OpenSSH 4.4p1, an ExitOnForwardFailure option is added so that ssh exits with a non-zero value if port forwarding requests fail.
So looks like smuxi can only use that option if OpenSSH is >= 4.4p1
Updated by Mirco Bauer 5829 days ago
Create ~/.config/smuxi/ssh-wrapper.sh:
#!/bin/sh SSH_PARAMS=$(echo "$@" | sed 's/-o ExitOnForwardFailure=yes //') echo "SSH_PARAMS: '$SSH_PARAMS'" ssh $SSH_PARAMSAdd this to your engine section in ~/.config/smuxi/smuxi-frontend.ini:
SshProgram = $HOME/.config/smuxi/ssh-wrapper.sh
(replace $HOME with the path of your home directory)
Updated by Mirco Bauer 5612 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 9ac304d745ee5659e9ff50d34a6ba71ae1fe6de3.