Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use a proxy #2104

Closed
cyberduck opened this issue May 19, 2008 · 5 comments
Closed

use a proxy #2104

cyberduck opened this issue May 19, 2008 · 5 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented May 19, 2008

06daabf created the issue

Hi,

I think it would be really nice if you supported using a proxy for the connection. OpenSSH has proxy support. Basically, the proxy support that OpenSSH has, is that you can specify a command line tool that will work as a proxy. The proxy tool is supposed to take stdin/stdout and just pipe it through. So, then you can download an HTTP proxy tool that will proxy through HTTP to get to internal servers on your network, without anyone knowing that they are even available, because they are not exposed.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 19, 2008

@dkocher commented

Set a SOCKS proxy in the System Network Preferences.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 19, 2008

06daabf commented

That isn't what I was thinking. Mainly because that would change the proxy for the entire system, not just Cyberduck. I was thinking more along the lines of a proxy ONLY for ssh connections, like OpenSSH does.

For one thing, the proxy for me is an HTTP proxy. That proxy ONLY allows proxying of SSH connections to the internal network, not other external hosts.

For example...
Apparently, there is no need for a DNS record for any server you want to connect to. You can just have an '/etc/hosts' entry on the proxy server.
So, any "ssh" connections to a host on somedomain.ca, or proxydomain.ca, will get run through the "proxytunnel" command, which happens to proxy through apache at sshproxy.proxydomain.ca:80.

My ~/.ssh/config

Host *.somedomain.ca
DynamicForward 1080
ProxyCommand proxytunnel -v -p sshproxy.proxydomain.ca:80 -d %h:%p -H "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)\n"
ServerAliveInterval 30
Host *.proxydomain.ca
DynamicForward 1080
ProxyCommand proxytunnel -v -p sshproxy.proxydomain.ca:80 -d %h:%p -H "User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)\n"
ServerAliveInterval 30

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 19, 2008

06daabf commented

Oops, sorry, the new lines didn't get put in properly.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 22, 2008

@dkocher commented

#12025.

@cyberduck cyberduck closed this Jul 22, 2008
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 10, 2010

4acee99 commented

#12025 is an HTTP proxy, which works if the proxy is at the client (CyberDuck) side. However, SSH ProxyCommand is for remote proxies, eg where you have a server contactable only via a SSH host.

#2865 is a more relevant ticket for those looking for SSH ProxyCommand support.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants