Q : What are the special features supported by RaidenFTPD?

A : RaidenFTPD supports the following commands via commmand connection , and the commands marked as red are extended ftp features and some of them are even non-rfc compliant , if you are writing your own ftp client program you can consider detecting RaidenFTPD and making use of the extended commands and make your ftp client to work better with RaidenFTPD

Setting exact date and time for a file

MDTM YYYYMMDDHHMMSS /path/filename

YYYY = Year MM = Month DD = Day HH = Hour MM = Min SS = Second

/path/filename is full or relative filename , it can contain space characters

Getting exact date and time for a file

MDTM /path/filename

/path/filename is full or relative filename , it can contain space characters

You will get a reply from the ftp server , telling you the file date and time in the YYYYMMDDHHMMSS format

Setting the ftp client type

CLNT Client_Name Version

After the ftp client sends the command to the RaidenFTPD , the RaidenFTPD can recognize the ftp client type and display it in the server monitoring console

Setting data connection security level

PROT C or PROT P

If the ftp client is connected via SSL , it can alter the Data Connection security level at any time by sending PROT C or PROT P , the 'C' means Clear - neither Integrity nor Privacy , and the 'P' means Private - Integrity and Privacy

Setting protection buffer size

PBSZ 0

According to RFC , this command 'PBSZ 0' must be send before any PROT command , however it is only a dummy command in RaidenFTPD which is ignored

Beginning to negotiate explicit SSL connection

AUTH SSL

If a ftp client is connecting to the RaidenFTPD on the explicit SSL port , the server will reply 234 AUTH Command OK. Initializing SSL connection. after the server receives this AUTH SSL command , and then begin to negotiate SSL connection with the ftp client

Bouncer specific command : setting client source IP address

IDNT *@IP:IP

This command is only allowed from the bouncer's IP addr. , and it must be sent before the USER xxxx command , with this IDNT command , checking client's IP addr. is possible even if all the clients are connected from bouncer , note that the bouncer program must disallow ftp client to send this command directly to the server otherwise there will be security risk

Getting the RaidenFTPD features list

FEAT

the server will return a list of currently supported extended features to the ftp client , the ftp client can then easily identify RaidenFTPD because of its unique features

Setting the desired ftp message language

LANG EN;FR;JA;DE;IT;SV;ES;RU;ZH-TW;ZH-CN

i.e. LANG ZH-TW , LANG EN

RaidenFTPD has built in 9 languages of message files , ftp clients can send this command to server to request for changing the message language on the fly , note that changing to the 'custom language message files' is not allowed for security reason

Getting the CRC32 value of a uploaded or downloaded file

XCRC "FileName" StartPos Length

i.e. : XCRC "XXX.ZIP" 0 1356

the server will return the CRC32 value of any specified file , note that the filename must be quoted , and the start position is usually 0 and the end position is usually the end of the file - 1

Getting the MD5 value of a uploaded or downloaded file

XMD5 "FileName" StartPos Length

i.e. : XMD5 "XXX.ZIP" 0 1356

the server will return the MD5 value of any specified file , note that the filename must be quoted , and the start position is usually 0 and the end position is usually the end of the file - 1

Turning the server into UTF8 mode ( RFC-2640 compliant )

OPTS UTF8 ON

OPTS UTF8 OFF

the server will return 220 UTF8 OPTS ON. , and begine to accept and return commands / dir listing ... etc , using UTF8 encoding .

Note1. the only 100% working FTP client for UTF8 is SmartFTP at this moment

Note2. RaidenFTPD does not grant IE6 to use this command at this moment because it's not fully implemented in IE6

Changing server's default SSL/TLS negotiation method for data connections

SSCN ON

SSCN OFF

SSCN ON : turning the server to use ssl_connect client negotiation method for RETR/STOR/APPE command

SSCN OFF : turning the server to use ssl_accept server negotiation method for RETR/STOR/APPE command

Note1. for LIST/NLST commands , it is always using ssl_accept server negotiation method

Note2. Without sending this command , the server is always using ssl_accept server negotiation method for all commands after data connection is made

Note3. This is only effect for users who connected using SSL/TLS command session and while not using clear data channel (PROT C)

That's ALL