mirror of
https://github.com/curl/curl.git
synced 2025-01-30 14:22:33 +08:00
Providing an explicit bind address besides the port for dynamic application-level
port forwarding, our socks port, prevents ssh from running on some systems. By default, ssh binds local port forwardings to the loopback address, since this was the address being given as the explicit bind address, now it isn't given.
This commit is contained in:
parent
ebce0a16f6
commit
788de4f7ba
@ -1105,7 +1105,7 @@ sub runsocksserver {
|
||||
}
|
||||
|
||||
my $flag=$debugprotocol?"-v ":"";
|
||||
my $cmd="ssh -D ${HOSTIP}:$SOCKSPORT -N -F curl_ssh_config ${USER}\@${HOSTIP} -p ${SSHPORT} -vv >log/ssh.log 2>&1";
|
||||
my $cmd="ssh -D $SOCKSPORT -N -F curl_ssh_config ${USER}\@${HOSTIP} -p ${SSHPORT} -vv >log/ssh.log 2>&1";
|
||||
logmsg "TRACESSH:runsocksserver: calling startnew with cmd: $cmd\n";
|
||||
my ($sshpid, $pid2) =
|
||||
startnew($cmd, $pidfile, 15, 1); # start the server in a new process
|
||||
|
Loading…
Reference in New Issue
Block a user