This is turning out to be quite a deviation from the original code. Figured that if there's a need for an ftp server written in node.js, one probably needs to tack on custom functionality, otherwise they'd just use vsftpd. So my goal is to lay the groundwork for a basic FTP server, with all the right hooks in place for customizing operations.
I assume you'll want to customize:
- User authentication (user and pass commands)
- Base folder for file operations
- What happens when certain file commands are performed
For my specific needs (at work) we needed custom user authentication, to sandbox all the file operations, and to run special code when a file is uploaded.
- Fire more events to allow customizations: directory changes, file uploads, etc
- None at the moment
These are known to work (or mostly work)
- Passive data connection establishment
- Non-passive data connection establishment
- CWD - change working directory
- DELE - delete file
- LIST - had to construct the list format programmatically because output from
ls -lwasn't being processed by FireFTP
- MKD - make directory
- RMD - remove directory (and contents)
- STOR - upload
- RETR - download
If a command is not listed, I probably haven't tested it yet.
See test.js for an example.
Then implement the following event callbacks with logic you need performed:
- command:user - Same as command:pass above, but first parameter will be the username that was sent from the client.
- command:pass - Sends three params. The first is the password. The second is a callback to be called if you determine the password is correct ... pass the username as the first parameter to this callback. Call the second if incorrect.
Also, don't run node as root just so you can get access to the FTP port. We run our node FTP server as an unprivileged user and perform port-forwarding with iptables. The following should work for you as well:
iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 21 -j REDIRECT --to-port 10000
Added LICENSE.txt with MIT license. Original code base had none, my changes are a pretty big deviation, and people have been asking.
Tested passive and non-passive data connections and found some issues, so I did some re-working.
Some things that might be nice:
- Figure out how it should be run, maybe as root first but execs to another user
- Fork new process when client connects and authenticates
Forked from http://github.com/billywhizz/nodeftpd Andrew Johnston - http://blog.beardsoft.com/node-ftp-server-initial-release
Andrew's initial release was tested about node.js 0.1.21 In the few short months since that release, node.js has changed quite a bit to where it is now, at time of writing 0.1.33
Changes made to nodeftp are as follows:
- POSIX module has now been moved to FS (0.1.29)
- File module has been removed (0.1.29)
- sys.exec callback system seems to have changed??
- as such quite a lot of moving about and rehacking had to take place:
- tcp has changed function names and listeners
- Rewrote ftptest.js as well
- Changed ports to 7001/7002 so I can test without being root
Also, not tested in Passive mode yet, but I think it works??
One thing I had problems with was the root filesystem of the FTP server. Even though I was running the ftpd.js from /home/rob/workspace it changed it to "/". This meant that if I tried to get the SIZE of a file, eg: /home/rob/workspace/file.txt it tried to get the SIZE of /home/rob/workspace//home/rob/workspace/file.txt I narrowed this down to the dummyfs.js functionality, but then if I changed the dummyfs root there was repeating of the path names
- Fix the repeating file paths problem
- Add in non-anonymous logins
- Implement non-implemented functionality (see ftpd.js TODO list)
- Add in proper error checking
- Test in passive mode
Updated for node v0.1.98