#Winscp port password

#Winscp port password

Username and password authentication is supported for HTTP proxies and SOCKS5 proxies.

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.Īuthentication is not fully supported for all forms of proxy: You can enter a username and a password in the User name and Password boxes, which will be used if your proxy requires authentication. The most typical method is USER Autodetect button to autodetect proxy settings. The methods differ by sequence of commands needed to instruct the proxy to connect to target host. 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.įor FTP protocol set of methods to connect over FTP proxies is supported. This type of proxy is not supported for FTP, WebDAV and S3 protocols. When the session is started, instead of creating a TCP connection, WinSCP runs the specified command, and uses its standard input and output streams. Selecting Local allows you to specify an arbitrary command on the local machine to act as a proxy.

Selecting Telnet allows you to tell WinSCP to use this type of proxy, with the precise command specified. Many firewalls implement a less formal type of proxy in which a user can make a Telnet or TCP connection directly to the firewall machine and enter a command such as connect 22 to connect through to an external host. Selecting SOCKS4 or SOCKS5 allows you to proxy your connections through a SOCKS server. Selecting HTTP allows you to proxy your connections through a web server supporting the HTTP CONNECT command, as documented in RFC 2817.

In this mode no proxy is used for the connection.

First, select what type of proxy you want WinSCP to use for its network connections.