Download Buru SFTP Server 2.16.0

We have released Rebex Buru SFTP Server v2.16.0. Here is an overview of changes, fixes and improvements.

Technological Update

Buru SFTP Server is built on .NET platform, which provides the foundation for its security and reliability. With this release, we've made several key upgrades to ensure compatibility with the current .NET version and support long-term stability for our users.

In alignment with Microsoft's .NET lifecycle, we have transitioned Buru SFTP Server to .NET 8 (LTS), as .NET 6 support ended on November 12, 2024. You can read more about this change in the official .NET 6 support policy.

This transition enables us to continue delivering the latest .NET security updates to our users. However, it also means that Windows 7 and Windows 8 are no longer supported from this version on as these are not officially supported by .NET 8. For more details on .NET 8, including its support timeline, visit the official .NET 8 support page.

Library Upgrades

In addition to updating our framework, we’ve also upgraded the libraries that Buru SFTP Server relies on, including advanced logging features powered by Serilog.

For more in-depth information on these features, refer to the Buru SFTP Server logging documentation.

FTP passive mode port and external address configuration (2.15.5)

In FTP passive mode, the client initiates both the command and data connections to the server. This approach is particularly beneficial when the client is behind a firewall or NAT (Network Address Translation) device, as it avoids the complications associated with incoming connections from the server.

Previously, the server would choose ports for passive mode connections from the dynamic port range assigned by the operating system. This range typically spans from 49152 to 65535.

With the latest release of Buru SFTP Server, administrators can now configure the FTP passive mode port range and specify the external IP address directly within the server settings.

The configuration can be accessed through the Web Administration interface under the FTP Settings section or configured directly in the config.yaml file.

Bug fixes

Fixed user database issue when some users couldn’t be loaded or updated (2.15.6)

We addressed an issue where user retrieval from the internal database sometimes failed due to indexing issues within the database, causing unpredictable behaviors and errors.

This manifested in various ways, including:

• Inability to load specific user details
• Failed attempts to delete certain users
• Misleading error messages when creating a new user with an existing username

We have temporarily resolved this issue by removing the problematic index. However, a permanent solution will be implemented in the next major release when the database library is updated. The current version does not include a full fix due to the potential for breaking changes.

Added no-cache HTTP header to Web Admin responses to prevent displaying outdated content (2.15.6)

The Microsoft Edge browser has been observed to load content directly from its cache without checking for updates (e.g., using If-Modified-Since), unlike other browsers. This behavior can lead to users viewing outdated content.

To address this, we added the no-cache directive in the HTTP headers, instructing browsers to always verify with the server before using a cached page version.

For a complete list of fixes and improvements, see the Release notes.

You can report issues and submit feature requests on our Github issue tracker.

For discussions and specific problems, please continue using our support forum.