
- #Filezilla server 1.2.0 how to
- #Filezilla server 1.2.0 update
Configuration data that cannot be serialized now prevents an incomplete output file from being written to disk.
Admin UI: The system_user's name cannot be edited anymore (rightly so).Admin UI (macOS): Implemented workarounds for some wxWidgets glitches and malfunctions.Admin UI: Fixed a crash in listener editor.
#Filezilla server 1.2.0 how to
Admin UI: The password fields in the configuration dialog now how show a hint to inform the user about how to keep the existing password. Communication with the impersonator child process is now asynchronous. Settings still residing under %LOCALAPPDATA%\filezilla-server are automatically migrated. #Filezilla server 1.2.0 update
This is to workaround the issue that when doing a Windows Update the settings could be wiped out.
MSW: If the service is running under the SYSTEM account, configuration files are now placed under %PROGRAMDATA%\filezilla-server. Server: The version number in the welcome messsage can now be manually suppressed by setting the "has_version" attribute of the message field in the configuration file to "false". Server: Implemented throttling of login attempts in case of too many failed attempts. Admin UI: Connection dialog did not remember the last used port if there are multiple saved entries for the same hostname with different ports. Admin UI: Fixed switching from "Use system credentials to log in" to "Require a password to log in" not applying. MSW: The notification area icon now displays again in all display scale factors. Fixed a crash if a session is closed and the data connection receives a connection error at the same time.
FileZilla Server 1.5.1 () Bugfixes and minor changes: