This article applies to BoKS 6.7 and 7.0.


These hotfixes solve a number of BoKS FTL (File Transfer Logging) related problems:

1) Uploading a file using the WinSCP client in SFTP mode triggers a bug in boks_sshd and the sftp-server, making the WinSCP client hang or produce an "Invalid response message type error". The file is uploaded and the upload is logged correctly to the audit log.

When uploading files using WinSCP, the WinSCP client sends both a write request (for the file upload) and a setstat request (for changing the access and modification time). The BoKS FTL feature, which is enabled by default as from BoKS 7.0, does not handle the setstat request correctly causing the boks_sshd to send a bad response to the WinSCP client.

OpenSSH clients and Putty do not send the setstat request when uploading a file (sftp put) and cannot set the access and modification time via a separate sftp command, so these clients are not affected.

2) While testing the hotfix for this problem, another BoKS FTL-related bug was discovered. This one also seems to be related to the WinSCP client sending multiple requests for a file upload. Sometimes multiple status messages from the WinSCP client get bundled into one status message when reaching boks_sshd, causing boks_sshd to send a bad response to the WinSCP client.

3) A bug in the BoKS scp binary acting as scp server, may cause the scp client to hang when downloading files if BoKS FTL is enabled. This has only been noticed when downloading from an AIX host.

Resolution / Workaround

Apply hotfix HFBM-0101 (for BoKS Manager 6.7) or HFBM-0102 (for BoKS Manager 7.0), available for download from the HelpSystems Community Portal.

The hotfix includes updated boks_sshd, scp and sftp-server binaries which will resolve the FTL-related bugs.

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: May 25, 2018