* The STAT command should output the same content such as LIST, but over the control connection. This patch fixes the implementation, so that the control connection is used. This fixes connections from Cyberduck * The STAT command used a bad multiline implementation that was not interpreted correctly by some clients. This patch fixes that * The multiline output added a superflous line that is now removed --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Reviewed-on: #182 Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: pkramme <me@pjkramme.de> Co-committed-by: pkramme <me@pjkramme.de>
server
A FTP server framework forked from github.com/yob/graval and changed a lot.
Full documentation for the package is available on godoc
Installation
go get goftp.io/server/v2
Usage
To boot a FTP server you will need to provide a driver that speaks to your persistence layer - the required driver contract is in the documentation.
Look at the file driver to see an example of how to build a backend.
There is a sample ftp server as a demo. You can build it with this command:
go install goftp.io/ftpd
And finally, connect to the server with any FTP client and the following details:
host: 127.0.0.1
port: 2121
username: admin
password: 123456
This uses the file driver mentioned above to serve files.
Contact us
You can contact us via discord https://discord.gg/ytmYqfNfqh or QQ群 972357369
Contributors
see https://gitea.com/goftp/server/graphs/contributors
Warning
FTP is an incredibly insecure protocol. Be careful about forcing users to authenticate with an username or password that are important.
License
This library is distributed under the terms of the MIT License. See the included file for more detail.
Contributing
All suggestions and patches welcome, preferably via a git repository I can pull from. If this library proves useful to you, please let me know.
Further Reading
There are a range of RFCs that together specify the FTP protocol. In chronological order, the more useful ones are:
- http://tools.ietf.org/rfc/rfc959.txt
- http://tools.ietf.org/rfc/rfc1123.txt
- http://tools.ietf.org/rfc/rfc2228.txt
- http://tools.ietf.org/rfc/rfc2389.txt
- http://tools.ietf.org/rfc/rfc2428.txt
- http://tools.ietf.org/rfc/rfc3659.txt
- http://tools.ietf.org/rfc/rfc4217.txt
For an english summary that's somewhat more legible than the RFCs, and provides some commentary on what features are actually useful or relevant 24 years after RFC959 was published:
For a history lesson, check out Appendix III of RCF959. It lists the preceding (obsolete) RFC documents that relate to file transfers, including the ye old RFC114 from 1971, "A File Transfer Protocol"
This library is heavily based on em-ftpd, an FTPd framework with similar design goals within the ruby and EventMachine ecosystems. It worked well enough, but you know, callbacks and event loops make me something something.