Tag Info

New answers tagged

0

with ProxyCommand its possible - because its just a set of shell commands: Host pro-* ProxyCommand ssh production-server nc 192.168.1.`echo "%h" | perl -pe 's/pro-//'` %p


0

It appears you do not have permission to open a socket on that server as implied by the -D switch... Normal ssh will work because it isn't opening a local socket for listening... A snippet from man ssh -D [bind_address:]port ... Only root can forward privileged ports. Dynamic port forwardings can also be specified in the configuration file. Looks like ...


1

Instead of wondering how to cope with a complex chain of SSH forwardings, separate the problems. Configure your system to have transparent access to every host. This is done once and for all in your ~/.ssh/config file. To teach SSH to use a machine as a proxy to another machine, declare a ProxyCommand . Host priv-server User user ProxyCommand ssh -W ...


1

This would be simple if you try a native sshfs which is recently added. Install sudo apt-get install sshfs sshfs -ttA user@pub-server ssh user@priv-server This will do the magic. For more infor see here Linux Journal


1

Instead use a more low level form of copying files by catting them locally, and piping that into a remote cat > filename command on priv-server: $ cat file1.txt | ssh -A user@pub-server 'ssh user@priv-server "cat > file1.txt"' or with compression: $ gzip -c file1.txt | ssh -A user@pub-server 'ssh user@priv-server "gunzip -c > file1.txt"' ...


2

That's about it, but you've inverted home and office. The point is that the office firewall rejects outgoing connections other than web traffic. But since HTTPS traffic and SSH traffic are both encrypted, it can't easily distinguish between them, so the firewall just blocks outgoing connections to ports other than 443 (the standard HTTPS port) and probably ...


1

I am not entirely clear on what the post talks about but I have been using something similar to redirect the http traffic over ssh from a remote server which does not support X forwarding. I do it as follows: ssh -L23000:localhost:23000 user@remotehost [remotehost] $ python -m SimpleHTTPServer 23000 Open browser on localhost and point it to ...


0

Found a solution and probably the cause. I suspect that proxy side has been enabled some kind of deep packet inspection (DPI) on 443 port, so only the "real" https requests can be accepted by proxy, all the other requests get a connection reset. The solution is to use a program called Stunnel that is able to wrap the https request in a SSL container, so ...


0

A snippet for local side, suitable for .bashrc: #!/bin/bash user=$1 host=$2 sshr() { # 1. connect, get dynamic port, disconnect port=`echo "exit" | ssh -R '*:0:127.0.0.1:52698' -t $1 2>&1 | grep 'Allocated port' | awk '/port/ {print $3;}'` # 2. reconnect with this port and set remote variable cmds="ssh -R $port:127.0.0.1:52698 -t $1 bash -c ...



Top 50 recent answers are included