Hi Christopher, > Using FTP in passive mode uses one port -- just the control connection. > This is what web browser FTP does by default. Sorry, that doesn't actually seem to be the case. passive ftp uses a seperate connection for data transfers just like active ftp - it's just established the other way round: in active ftp, the server opens a new connection to the client, in passive ftp, the client opens a 2nd connection to the server web browsers generally use passive ftp because most firewall setups allow outbound TCP connections to be established. Getting normal FTP data connections right in a firewall is much more complicated and thus often disabled. > Type "quote PASV" at your ftp> prompt. That won't get you anywhere since it'll just tell the server to listen for an incoming data connection without setting the client up to use it. The ftp PASV command is sent by the ftp client for each data connection it wants to establish with the server; the server answers with something like "Entering Passive Mode (192,168,0,1,16,41)", where the numbers specify the ip address and port number the server is listening on for the data connection. > If you want secure file transfer, use scp that comes with > ssh or zmodem through a ssh connection. Yep, good advice. If you're only interested in keeping your username/password save, and if the FTP server doesn't check if a data conenction comes from the expected client IP address, you can get away with tunneling the ftp control connection over ssh and using passive ftp to establish data connections directly from client to server. Bye, Martin "you have moved your mouse, please reboot to make this change take effect" -------------------------------------------------- Martin Bene vox: +43-316-813824 simon media fax: +43-316-813824-6 Andreas-Hofer-Platz 9 e-mail: mb@sime.com 8010 Graz, Austria -------------------------------------------------- finger mb@mail.sime.com for PGP public key - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu
