Rebex Buru SFTP Server 2.17.0: SSH configuration improvements

Download Buru SFTP Server

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

SSH configuration improvements

SSH tunneling configuration changes (2.17.0)

SSH tunnels have been supported since early versions of Buru SFTP Server, however, without any Web Admin configuration and prone to endpoint conflicts.

We fixed the conflict issue and simplified the configuration by moving it from sshTunneling section to bindings section, on the same level as SFTP, SCP/Shell and FTP protocols:

# before
sshTunneling:
  enabled: true
  bindings:
    - { port: 22, ipAddress: 0.0.0.0 }

# after
bindings:
  - { port: 22, ipAddress: 0.0.0.0, sshTunnel: true, ... }

SSH tunneling can now be also enabled or disabled in the Web administration and is disabled by default.

Warning is shown on startup when sshTunneling section is present in the configuration file, its values are now ignored.

SSH shell configuration defaults now configurable using Web administration (2.17.0)

Default values for SSH shell home directory and SSH shell executable path are now configurable using Web administration. These values can be overridden per user.

Improved support for displaying user's public keys (2.17.0)

Based on a client's feedback, we improved the way user's public SSH keys can be displayed:

• User's details in Web administration now show the user's public key with SSH algorithm prefix to make it easier to re-import to other applications, e.g. authorized_keys file.
• Output of burusftp user inspect command now also contains full SSH public key, with SSH algorithm prefix.

Minor changes and fixes

• Web Admin
  • Fixed an issue when SSH shell settings were sometimes not editable (2.16.1)
• Installer
  • Fixed missing prompt to remove all configuration files when uninstalling. (2.16.1)

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.