This is the list of known issues for the current release of SFTPPlus.
[#1054] No support for non-ASCII characters in the server’s installation path.
In order to ensure correct operation of SFTPPlus, please avoid using special Unicode characters in the installation folder path.
[#1245] Events logged in Windows Event Logger are listed without a specific Windows description.
Events logged in Windows Event Logger are listed without a human friendly Windows description. Nevertheless, the data exported as XML is detailed and complete.
Copying a Local Manager URL from within an authenticated session and pasting it in an unauthenticated session will prompt for the login page. After a successful authentication, the new session will redirect to the start page, not to the initial requested page.
Collaborative configuration from multiple separate Local Manager sessions is not supported. The Local Manager allows opening multiple administration sessions, but assumes that only one session will change the configuration. Changes in one session will not be automatically reflected in the other session. You will need to refresh the page in order to see the changes.
Internationalized Domain Names (http://en.wikipedia.org/wiki/Internationalized_domain_name) are not supported. The server itself and all systems with which it interacts should use ASCII domain names.
[#1400] When the server fails to start, it will only emit the general log event 20002 to signal that the server is stopping, without sending dedicated 20078 events for each service that was initially started. Service stop events are still emitted when a service is stopped at running time from the Local Manager or when the server is stopped in a normal way.
[#1470] The Local Manager will not warn when adding multiple services, accounts, and groups with the same name. No error is generated because internally the server uses UUIDs for addressing these items.
[#1547] When creating a new FTP or Implicit FTPS service, the passive port range is not updated in the GUI. After the new service creation has been applied on the server, the passive port range is available for changes.
[#1588] On service start/stop the audit entries for these actions have no field mentioning the administrator requesting the action.
[#1787] HTTP Post Request log handlers accept HTTPS URLs, but do not validate the SSL connection.
[#1935] In the HTTP/HTTPS file service, actions can only be triggered by explicitly clicking on buttons. Actions cannot be triggered using the ‘Enter’ keyboard key.
[#1946] On Windows systems, the installation will not generate an install log file when running in silent mode.
[#2057] SFTP symbolic links on Windows systems only work when using absolute paths.
When the server does not have write permissions to the configuration file and an administrator applies changes from the Local Manager, changes are applied, but they do not persist in the configuration. If you fix the permissions while the server is still running, there is no option to force a new save to the configuration file, other than making another change and applying it. Then, all previous changes will also be saved.
[#1374] When accessing the Local Manager, authentication will fail if using credentials saved by the Firefox Password Manager. You’ll have to manually re-enter the password.
[#2311] When a file is created and then moved immediately, the moved event is emitted before the create event. The correct behaviour is to only emit a single create event with the final path, and ignore the temporary create and move events.
[#2383] On Windows systems, execute_before, execute_after_success, and execute_after_failure cannot be configured with a path containing non-ASCII characters. Also, when any execute_* action is called for files containing non-ASCII characters, the passed file names are corrupted.
[#2389] execute_before, execute_after_success, and execute_after_failure are not yet supported on Windows XP and Windows Server 2003.
[#2547] When a password is used to import a private key which is not password-protected, the Local Manager will still inform you that the key is password-protected.
[#2714] On HP-UX systems, the SQLite DB support does not work.
[#2715] On HP-UX systems, self-signed certificates generated during the initialization of the configuration are not accepted by the HTTPS and Local Manager services. However, they do work with the FTPS service.
[#2716] On HP-UX systems, the SFTPPlus process name is exposed using the internal name INSTALL_PATH/bin/python -m chevah.server.__init__ instead of the usual sftpplus-service name.
[#2717] On HP-UX systems, accounts with passwords stored in the /etc/shadow file are not supported.
[#2745] On HP-UX systems, authenticating accounts using PAM is not supported.
[#2747] On HP-UX and AIX systems, the server cannot execute external commands.
[#3107] On AIX systems, there is a performance issue with the default, one-way encrypted, passwords for application accounts. Usually, to harden short passwords, plain text passwords are passed through 80,000 rounds of encryption. Unfortunately, this results in degraded performance on AIX. As a workaround, on AIX we have reduced the number or encryption rounds to 5.000, which is the default number of rounds for the original SHA-256 crypt scheme. To compensate for the reduced number of encryption rounds, longer passwords should be used.
[#3134] On Solaris 11 systems, the PAM authentication method is not yet supported.
[#91] FTP restart of interrupted transfer command REST is not yet implemented.
[#92] FTP Trivial Virtual File Store (TVFS) is not yet implemented.
[#93] FTP listing for machine processing commands (MLST and MLSD) are not yet implemented.
[#94] FTP session reinitialization command (REIN) is not yet implemented.
[#1160] FTP zlib compression command MODE Z is not yet implemented.
[#1161] FTP cyclic redundancy check using the CRC-32 algorithm XCRC is not yet implemented.
[#2357] FTP unique store command (STOU) is not yet implemented.
[#3294] When the file was successfully transferred but failed to be removed from the source location, the transfer is considered failed but source file is archived as a success.
[#3371] File dispatcher will not work for upload event for which the client is making the initial upload request under a provisional file name which is change once the file is successfully uploaded.
[#3379] hmac-sha2-512 is not yet available in our SSH implementation due to an interoperability issue with the OpenSSH client.
[#2135] SCP server implementation does not handle errors reported by the client side during file get / download operations.
[#3412] Files which are uploaded to the SFTPPlus using FTP or FTPS and for which the data channel is closed before the file was completely uploaded are reported as successfully uploaded. This is because when the file was successfully uploaded the data channel is closed in the same way.
[#2975] When using Syslog over TCP and the TCP connection is lost, SFTPPlus will try to reconnect, but all events emitted while trying to connect are discarded.
[#3478] When certificate revocation lists are configured, they will only work when the CA certificates are stored in a single file. Storing CA certificates in a single directory is not yet supported.
[#3461] On Windows, it is not possible to load CA files stored on paths containing non ASCII characters.
[#3494] When CRL distribution points (CDP) are configured only the first advertised HTTP CRL is used.
[#3543] Remote Windows share paths are not supported for account home folder paths.
[#3551] Estimated rotation time is recalculated every time when an event handler (configured to rotate a file at certain time interval) is restarted.
[#3557] Estimated rotation time is recalculated every time when an event handler (configured to rotate a file on certain day of a month) is restarted.
[#2672] Locations for FTP, FTPS and SFTP protocols will perform the connections using a fixed timeout of 10 seconds.
[#3563] FTPS locations don’t yet support sending the client certificate as part of the TLS/SSL negotiation for the secured command connection nor when securing the data connection.
[#3566] FTPS locations are not checking the identity of the remote server for the command of the data connections.
[#3122] FTPS locations don’t yet support defining custom cipher lists or TLS/SSL methods.
[#3602] Estimated rotation time is not appropriately adjusted if the system time was put back.
[#3604] Log rotation occurs only when a new event is made.
[#3594] FTPS CCC command is only supported with Explicit FTPS for both client and server side. It is not yet supported for Implicit FTPS.
[#3599] FTPS CCC command is supported by the server-side only in active mode, while on the client-side only passive mode is supported. Please contact us if you need to communicate with a peer FTPS implementation which don’t support the above described modes.