Which means you are potentially sharing domain logins with the world which is always a bad idea.įTPS, on the other hand, encrypts all communication if setup correctly, including transmission of username and password during the authentication of a new session. With FTP, user credentials are sent to the server in plain-text and anyone snooping would quickly see your users’ login credentials. You should ONLY enable Active Directory authentication if you are running FTPS and you should NEVER enabled Active Directory authentication if you are running FTP. Before I jump into that though, a word of security caution… However, Filezilla is open-source and some enterprising users have a version of it released on source-forge which makes use of OpenLDAP to support Active Directory authentication. Which means -NO- Active Directory authentication and no SSO for your Windows users.
It’s simplicity however is also its flaw.īy default, Filezilla server only supports user accounts local to the application itself. While I don’t care for the Filezilla client (for several reasons, one of them being that it stores saved passwords in plaintext on your machine), the server software is okay… it runs nicely on Windows Server 2012 R2 and it is significantly easier to manage vs. If you haven’t use Filezilla Server before it is a pretty decent and easy to manage FTP/FTPS solution.
0 kommentar(er)
