Differences
This shows you the differences between the selected revisions of the page.
| 2007-01-31 | 2008-04-16 | ||
| advanced options (martin) | 4.1 Support for "local proxying", where a network connection is replaced by a local command. (martin) | ||
| Line 1: | Line 1: | ||
| ====== Proxy Tab ====== | ====== Proxy Tab ====== | ||
| - | //Proxy tab// allows you to configure WinSCP to use various types of proxy in order to make its network connections.· | + | //Proxy tab// allows you to configure WinSCP to use various types of proxy in order to make its network connections. |
| &screenshotpict(login_proxy) | &screenshotpict(login_proxy) | ||
| Line 14: | Line 14: | ||
| Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as ''connect myhost.com 22'' to connect through to an external host. Selecting //Telnet// allows you to tell WinSCP to use this type of proxy. | Many firewalls implement a less formal type of proxy in which a user can make a Telnet connection directly to the firewall machine and enter a command such as ''connect myhost.com 22'' to connect through to an external host. Selecting //Telnet// allows you to tell WinSCP to use this type of proxy. | ||
| + | |||
| + | Selecting //Local// allows you to specify an arbitrary command on the local machine to act as a proxy. When the session is started, instead of creating a TCP connection, WinSCP runs the specified command, and uses its standard input and output streams. | ||
| + | |||
| + | This could be used, for instance, to talk to some kind of network proxy that WinSCP does not natively support; or you could tunnel a connection over something other than TCP/IP entirely. | ||
| ===== Username and Password ===== | ===== Username and Password ===== | ||
| Line 23: | Line 27: | ||
| * With HTTP proxying, the only currently supported authentication method is "basic", where the password is sent to the proxy in plain text. | * With HTTP proxying, the only currently supported authentication method is "basic", where the password is sent to the proxy in plain text. | ||
| * SOCKS 4 can use the //Username// field, but does not support passwords. | * SOCKS 4 can use the //Username// field, but does not support passwords. | ||
| - | * You can specify a way to include a username and password in the //Telnet// proxy command. | + | * You can specify a way to include a username and password in the //Telnet/Local// proxy command. |
| - | ===== Telnet Proxy Command ===== | + | ===== Telnet/Local Proxy Command ===== |
| If you are using the //Telnet// proxy type, the usual command required by the firewall's Telnet server is ''connect'', followed by a host name and a port number. If your proxy needs a different command, you can enter an alternative here. | If you are using the //Telnet// proxy type, the usual command required by the firewall's Telnet server is ''connect'', followed by a host name and a port number. If your proxy needs a different command, you can enter an alternative here. | ||
| + | |||
| + | If you are using the Local proxy type, the local command to run is specified here. | ||
| In this string, you can use ''\n'' to represent a new-line, ''\r'' to represent a carriage return, ''\t'' to represent a tab character, and ''\x'' followed by two hex digits to represent any other character. ''\\'' is used to encode the \ character itself. | In this string, you can use ''\n'' to represent a new-line, ''\r'' to represent a carriage return, ''\t'' to represent a tab character, and ''\x'' followed by two hex digits to represent any other character. ''\\'' is used to encode the \ character itself. | ||