2011年4月13日 · SFTP is sometimes called "Secure FTP" which leads to a common confusion with FTPS (which is called "Secure FTP" too). Generally: SFTP - SSH File Transfer Protocol - usually runs over TCP port 22. FTP - plain, old file transfer protocol - usually runns over TCP port 21 (+ opens separate ports for data transfer) FTP/SSL - FTP over TLS/SSL channel.

SFTP runs on top of SSH, which - by convention - uses the well known port of 22. The well known port, however, is only a convention - there is no way (and indeed no point) in preventing the server from listening on a different port. (i.e. you can run the server on port 63251 and it would still work, as long as the clients are connecting to that ...

This is how the FTP client knows you need to create a secure connection, and why I keep repeating that the port number is irrelevant. Continue to use your username and password as you've set it up (I am using anonymous and no password), and insert your port number at the end, though if you are using the FTPS default of 990, Filezilla tends to ...

the client tells port 21 what upper-bound port to open and so you can configure the client to say "control is on port 2000 or 2001" and then the server will open outbound port 2000 or 2001. most FTP clients support defining a specific range of ports for "control" to be on and that makes firewall definitions easy. –

You will certainly have issues with FTP/SSL in either passive/active mode if your firewall rules are too strict. On active mode, you only need to open ports 20/21 inbound and keep the state to outbound, but it will not work well with many users, but you don't need to worry about using ftp-proxy tools or anything.

As others have pointed out, changing the port number does not offer you much security. I'd like to add that changing the port number may actually be detrimental to your security. Imagine the following simplified scenario. A cracker scans 100 hosts. Ninety-nine of these hosts have services available on these standard ports:

2017年11月2日 · If you want to ask a question here you need a way better information. + SFTP and "FTP over SSH" are two completely different things. Again, you need a way better information, before asking here. + Regarding port encryption: The first network component after the client (what is probably the firewall) needs to know the port number.

2011年5月18日 · I suppose you could limit the passive port range to one single port. In fact you can see in this question that small port ranges are used in practice. Theoretically, to support multiple concurrent connections you only need the 4 values: local IP, local port, remote IP, remote port to be unique. This is how you discern between different connections.

2017年3月16日 · Also I did eventually get a functioning setup by setting the chroot location to %h, and then mounting the /var/www/html inside /home/ftp/. Now I can connect with SFTP. But I do still also see the .ssh folder in /home/ftp, and of course I can't make that inaccessible, or

2013年3月7日 · Can a ftp server listen on any other port than 21 (default control port to which any FTP client initiates the connection to)? If yes, how does the client know on which port it has to initiate the connection to? Is it an RFC violation to use non-default control port on the server? Please note that I am not asking about server side data port.