[ https://issues.apache.org/jira/browse/FTPSERVER-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson updated FTPSERVER-367: ---------------------------------------- Fix Version/s: 1.1.0 (was: WISHLIST) Let's implement this one for 1.1.0 > RFC: FTP HASH command (similar to MD5, which is already supported) > ------------------------------------------------------------------ > > Key: FTPSERVER-367 > URL: https://issues.apache.org/jira/browse/FTPSERVER-367 > Project: FtpServer > Issue Type: New Feature > Reporter: Ant Bryan > Priority: Trivial > Fix For: 1.1.0 > > > According to http://mina.apache.org/ftpserver/documentation.html , the > MD5/MMD5 FTP commands from draft-twine-ftpmd5-00 are supported. > Unfortunately, MD5 and other FTP hashing commands (XMD5, XSHA, XSHA1, > XSHA256, XSHA512, SITE SHOHASH, SITE CHECKSUM, etc) have not been formally > specified, leading to non-interoperability and confusion. > A new draft which intends to reach RFC status is underway: > http://tools.ietf.org/html/draft-bryan-ftp-hash > It would be very helpful, if this draft could be reviewed and your comments > provided to improve it. > Here is a quick overview. > Requesting hash: > HASH filename.ext > HASH server response with Positive Completion code and the requested > hash using the currently selected algorithm: > 213 80bc95fd391772fa61c91ed68567f0980bb45fd9 > Changing HASH algorithms: > C> OPTS HASH SHA-512 > S> 200 SHA-512 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.