If I pester them, I could point to the 213 as what they should do, if you agree with it. Their docs say MDTM responds with 213, which it doesn't. If I also post a ticket to Titan about MDTM, would you prefer a 250 response, or a 213 response similar to MFMT? Their server is great, but their docs are poor. Since setting time with MDTM is not spec'ed, there is no spec'ed response code. A remote authenticated attacker could exploit this. Since this is a bit of red herring, assuming they'll fix MFMT, I'm happy with however you want to proceed: Titan FTP Server is vulnerable to a denial of service, caused by an error when handling certain commands. In the meantime, if you would like to get things consistent, I noticed that the BC3 file transfer sequence that sends MDTM accepts 200 but the touch command sending MDTM does not (which is what started this thread) Version: 20 (Release Date: July 9, 2021) Updated: Changed the default Passive Mode FTP Port Range to 28,000-30,000 to limit the number of open ports. I run Windows 7 圆4 and Titan FTP Server in both Active and Passive mode to share and synchronize data with my laptop and tablet. Serv-U MFT Server by Solarwinds SFTP server by /n software SFTPGo SFTPPlus SilverShield Syncplify Tectia SSH Server Titan FTP Server VShell Secure File. The right answer is for me to wait for that fix. I posted a ticket that they should accept it. Titan now accepts MFMT, but they fail on the decimal point and following digits. I learned that MDTM to set time is not technically correct, but I appreciate that you support it as a common behavior. Titan FTP Server has a WebUI that allows users to upload and download files quickly without any additional software or plugins. I'm pinning down both sides of the timestamps, but I'll still keep this thread about the response code behavior.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |