Hot answers tagged

4

First possibility is obvious (note the -t switch): ssh -t -i cloudkey -L 6000:localhost:6001 admin@54.152.188.55 -p 9000 \ "ssh -D 6001 -p 6666 localhost -l dancloud" With ProxyCommand it is more complicated on the first sight, but conceptually you need only one forwarding (netcat version is not advised anymore, using -W switch is more elegant): Host ...


2

I found the answer https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Proxies_and_Jump_Hosts SOCKS proxy via an Intermediate Host If you want to open a SOCKS proxy via an intermediate host, it is possible: $ ssh -L 8001:localhost:8002 user1@machine1.example.org -t ssh -D 8002 user2@machine2.example.org The client will see a SOCKS proxy on ...


2

You can start gpg-agent remotely and create remote UNIX socket port forwarding to your host and then use the gpg-agent locally. In short Connect to the server and start gpg-agent (if it is not running yet) and ensure it stays running. It is listening on socket defined in environment variable $GPG_AGENT_INFO. Store the path: eval `gpg-agent --daemon` ...


1

What you are doing there is at least 'complicated'. As far is i understood, you connect to one server, and tell it to sync to another server. For ease of use, you may specify port and user to use in the local ssh configuration for a particular host. for instance, if you add the following lines to the file ~/.ssh/config (/home/username2/.ssh/config) on the ...


1

You should be able to accomplish what you're looking to do with something similar to: ssh -i cloudkey -L 6000:localhost:6001 admin@54.152.188.55 -p 9000 -t "ssh -D 6001 -p 6666 localhost -l dancloud" the -t flag forces a pseudo-tty on the first machine and executes the remaining code on the first machine; in this case, ssh to the dancloud tunnel. The ...


1

Looks like you set up a some sort of proxy listening on TCP:3300 port and forwarding all the traffic to your remote Windows PC RDP (remote desktop) port. Then all traffic goes to TCP:3300 will be forwarded to remote Windows PC at RDP port, so you can connect to it with regular RDP client. You'll need to have existing network route to between Windows PC and ...



Only top voted, non community-wiki answers of a minimum length are eligible