Comments on: Basic Windows FTP Command Line Scripting http://www.pcmech.com/article/basic-windows-ftp-command-line-scripting/ Helping Normal People Get Their Geek On Wed, 15 Feb 2012 10:29:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: SenHuhttp://www.pcmech.com/article/basic-windows-ftp-command-line-scripting/comment-page-1/#comment-41267 SenHu Mon, 03 May 2010 14:55:01 +0000 http://1933839237#comment-41267 >> If someone found the scripting file in your C:\WINDOWS directory, they’ve got your FTP username and password.This is not correct. One solution is already proposed above (don't allow access to the batch file to anyone else but the author). But, that then makes it impossible to write a batch file usable by all.I use this script.http://www.biterscripting.com/helppages/SS_FTPUpload.htmlIt replicates the entire local directory to the FTP server. It creates subdirectories as necessary. And the good thing is, the FTP login and password are not hard-coded in the script. They are supplied by each user, when calling the script, as follows.script "C:/Scripts/SS_FTPUpload.txt" ftpserver("ftp.mycompany.com") ftplogin("login") ftppassword("password")Each user supplies his/her own login/password, making the script usable by all. >> If someone found the scripting file in your C:\WINDOWS directory, they’ve got your FTP username and password.

This is not correct. One solution is already proposed above (don’t allow access to the batch file to anyone else but the author). But, that then makes it impossible to write a batch file usable by all.

I use this script.

http://www.biterscripting.com/helppages/SS_FTPUpload.html

It replicates the entire local directory to the FTP server. It creates subdirectories as necessary. And the good thing is, the FTP login and password are not hard-coded in the script. They are supplied by each user, when calling the script, as follows.

script “C:/Scripts/SS_FTPUpload.txt” ftpserver(“ftp.mycompany.com”) ftplogin(“login”) ftppassword(“password”)

Each user supplies his/her own login/password, making the script usable by all.

]]> By: Jason Faulknerhttp://www.pcmech.com/article/basic-windows-ftp-command-line-scripting/comment-page-1/#comment-17904 Jason Faulkner Thu, 11 Dec 2008 18:22:36 +0000 http://1933839237#comment-17904 >>One final note: This is obviously not secure whatsoever. If someone found the scripting file in your C:\WINDOWS directory, they’ve got your FTP username and password.The security on a batch file is no different than the security of any other file... just set the properties so that only yourself (and obviously Administrators) can read it and you are all set. No need for the file to be in the Windows directory, it can be anywhere you like.I've been using this method for over a year as a way to automate moving our backups off-site. My script runs on a Terminal Server and I have the security of the BAT file locked down so that standard users cannot access it. >>One final note: This is obviously not secure whatsoever. If someone found the scripting file in your C:\WINDOWS directory, they’ve got your FTP username and password.

The security on a batch file is no different than the security of any other file… just set the properties so that only yourself (and obviously Administrators) can read it and you are all set. No need for the file to be in the Windows directory, it can be anywhere you like.

I’ve been using this method for over a year as a way to automate moving our backups off-site. My script runs on a Terminal Server and I have the security of the BAT file locked down so that standard users cannot access it.

]]> By: Markhttp://www.pcmech.com/article/basic-windows-ftp-command-line-scripting/comment-page-1/#comment-17869 Mark Thu, 11 Dec 2008 03:33:42 +0000 http://1933839237#comment-17869 FTP is an obsolete and outdated protocol. Anyone using FTP should seriously consider using WebDAV. Since DAV works over HTTP, you get all the benefits of HTTP that FTP cannot provide. For example: strong authentication, encryption, proxy support, and caching. It is true that you can get some of this through SSH, but the HTTP infrastructure is much more widely deployed than SSH. Further, SSH does not have the wide complement of tools, development libraries, and applications that HTTP does. DAV transfers (well, HTTP transfers) are also more efficient than FTP. You can pipeline multiple transfers through a single TCP connection, whereas FTP requires a new connection for each file transferred (plus the control connection). Do a Google search for BarracudaDrive, which is an easy to use WebDAV server. http://barracudaserver.com/products/BarracudaDrive/FileServer.lsp You do not need a client if using Windows or Mac since a client is integrated into the operating system. FTP is an obsolete and outdated protocol.
Anyone using FTP should seriously consider using WebDAV.
Since DAV works over HTTP, you get all the benefits of HTTP that FTP cannot provide. For example: strong authentication, encryption, proxy support, and caching. It is true that you can get some of this through SSH, but the HTTP infrastructure is much more widely deployed than SSH. Further, SSH does not have the wide complement of tools, development libraries, and applications that HTTP does.
DAV transfers (well, HTTP transfers) are also more efficient than FTP. You can pipeline multiple transfers through a single TCP connection, whereas FTP requires a new connection for each file transferred (plus the control connection).
Do a Google search for BarracudaDrive, which is an easy to use WebDAV server.
http://barracudaserver.com/products/BarracudaDrive/FileServer.lsp
You do not need a client if using Windows or Mac since a client is integrated into the operating system.

]]>