Differences
This shows you the differences between the selected revisions of the page.
| 2025-11-03 | 2026-06-02 (current) | ||
| Restored revision 1684919135. Undoing revision 1762141104. (martin) (hidden) | 6.6.2 Using “username” and “hostname” as one word (martin) | ||
| Line 28: | Line 28: | ||
| ===== [[username_password]] Username and Password ===== | ===== [[username_password]] Username and Password ===== | ||
| - | You can enter a username and a password in the //User name// and //Password// boxes, which will be used if your proxy requires authentication. | + | You can enter a username and a password in the //Username// and //Password// boxes, which will be used if your proxy requires authentication. |
| If WinSCP discovers that it needs a proxy username or password and you have not specified one here, WinSCP will prompt for it interactively in the terminal window. | If WinSCP discovers that it needs a proxy username or password and you have not specified one here, WinSCP will prompt for it interactively in the terminal window. | ||
| Line 36: | Line 36: | ||
| * With SOCKS5, authentication is via CHAP if the proxy supports it, otherwise the password is sent to the proxy in plain text. | * With SOCKS5, authentication is via CHAP if the proxy supports it, otherwise the password is sent to the proxy in plain text. | ||
| * With HTTP proxying, authentication is via "HTTP Digest" if possible, or "HTTP Basic". In the latter case, the password is sent to the proxy in plain text. | * With HTTP proxying, authentication is via "HTTP Digest" if possible, or "HTTP Basic". In the latter case, the password is sent to the proxy in plain text. | ||
| - | * SOCKS4 can use the //User name// field, but does not support passwords. | + | * SOCKS4 can use the //Username// field, but does not support passwords. |
| * You can specify a way to include a username and password in the //Telnet/Local// proxy command. \\ If you do so, and don't also specify the actual username and/or password in the configuration, WinSCP will [[ui_authenticate#proxy|interactively prompt for them]]. | * You can specify a way to include a username and password in the //Telnet/Local// proxy command. \\ If you do so, and don't also specify the actual username and/or password in the configuration, WinSCP will [[ui_authenticate#proxy|interactively prompt for them]]. | ||
| * Most FTP proxy methods do require authentication. | * Most FTP proxy methods do require authentication. | ||
| ===== [[command]] Telnet/Local Proxy Command ===== | ===== [[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 in the //Telnet command// box. | + | If you are using the //Telnet// proxy type, the usual command required by the firewall's Telnet server is ''connect'', followed by a hostname and a port number. If your proxy needs a different command, you can enter an alternative in the //Telnet command// box. |
| If you are using the //Local// proxy type, the local command to run is specified in the //Local Proxy Command//. | If you are using the //Local// proxy type, the local command to run is specified in the //Local Proxy Command//. | ||
| Line 47: | Line 47: | ||
| 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. | ||
| - | Also, the special strings ''%host'' and ''%port'' will be replaced by the host name and port number you want to connect to. The strings ''%user'' and ''%pass'' will be replaced by the proxy username and password (which, if not specified in the configuration, will be prompted for). To get a literal ''%'' sign, enter ''<nowiki>%%</nowiki>''. | + | Also, the special strings ''%host'' and ''%port'' will be replaced by the hostname and port number you want to connect to. The strings ''%user'' and ''%pass'' will be replaced by the proxy username and password (which, if not specified in the configuration, will be prompted for). To get a literal ''%'' sign, enter ''<nowiki>%%</nowiki>''. |
| If a Telnet proxy server prompts for a username and password before commands can be sent, you can use a command such as: | If a Telnet proxy server prompts for a username and password before commands can be sent, you can use a command such as: | ||
| Line 62: | Line 62: | ||
| If you are using a proxy to access a private network, it can make a difference whether DNS name resolution is performed by WinSCP itself (on the client machine) or performed by the proxy. | If you are using a proxy to access a private network, it can make a difference whether DNS name resolution is performed by WinSCP itself (on the client machine) or performed by the proxy. | ||
| - | The //Do DNS name lookup at proxy end// configuration option allows you to control this. If you set it to //No//, WinSCP will always do its own DNS, and will always pass an IP address to the proxy. If you set it to //Yes//, WinSCP will always pass host names straight to the proxy without trying to look them up first. | + | The //Do DNS name lookup at proxy end// configuration option allows you to control this. If you set it to //No//, WinSCP will always do its own DNS, and will always pass an IP address to the proxy. If you set it to //Yes//, WinSCP will always pass hostnames straight to the proxy without trying to look them up first. |
| - | If you set this option to //Auto// (the default), WinSCP will do something it considers appropriate for each type of proxy. Most types of proxy (HTTP, SOCK5, Telnet, and local) will have host names passed straight to them; SOCKS4 proxies will not. | + | If you set this option to //Auto// (the default), WinSCP will do something it considers appropriate for each type of proxy. Most types of proxy (HTTP, SOCK5, Telnet, and local) will have hostnames passed straight to them; SOCKS4 proxies will not. |
| The original SOCKS4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS4A) which does support it, but not all SOCKS4 servers provide this extension. If you enable proxy DNS and your SOCKS4 server cannot deal with it, this might be why. | The original SOCKS4 protocol does not support proxy-side DNS. There is a protocol extension (SOCKS4A) which does support it, but not all SOCKS4 servers provide this extension. If you enable proxy DNS and your SOCKS4 server cannot deal with it, this might be why. | ||
| - | If you want to avoid WinSCP making any DNS query related to your destination host name (for example, because your local DNS resolver is very slow to return a negative response in that situation), then as well as setting this control to //Yes//, you may also need to turn off [[ui_login_authentication#gssapi|GSSAPI authentication]] and [[ui_login_kex#gssapi|GSSAPI key exchange]] in SSH. This is because GSSAPI setup also involves a DNS query for the destination host name, and that query is performed by the separate GSSAPI library, so WinSCP can't override or reconfigure it. | + | If you want to avoid WinSCP making any DNS query related to your destination hostname (for example, because your local DNS resolver is very slow to return a negative response in that situation), then as well as setting this control to //Yes//, you may also need to turn off [[ui_login_authentication#gssapi|GSSAPI authentication]] and [[ui_login_kex#gssapi|GSSAPI key exchange]] in SSH. This is because GSSAPI setup also involves a DNS query for the destination hostname, and that query is performed by the separate GSSAPI library, so WinSCP can't override or reconfigure it. |
| These options are not available for [[ftp|FTP protocol]]. | These options are not available for [[ftp|FTP protocol]]. | ||
| ===== [[localhost]] Proxying Local Host Connections ===== | ===== [[localhost]] Proxying Local Host Connections ===== | ||
| - | Connections to the local host (the host name ''localhost'', and any loopback IP address) are not proxied by default. It is very unlikely that this behavior would ever cause problems, but if it does you can change it by enabling //Consider proxying local host connections//. ((&puttydoccite)) | + | Connections to the local host (the hostname ''localhost'', and any loopback IP address) are not proxied by default. It is very unlikely that this behavior would ever cause problems, but if it does you can change it by enabling //Consider proxying local host connections//. ((&puttydoccite)) |
| This option is not available for [[ftp|FTP protocol]]. | This option is not available for [[ftp|FTP protocol]]. | ||