June 12, 2023 in Releases by David Wiseman2 minutes
Config file encryption & config file backup retention
You can now encrypt the config file providing better protection for any sensitive information stored such as passwords and access keys. Ideally you should avoid storing any passwords in the config file but there are some situations where this is not possible. Using config file encryption will help keep this data secure.
See here for more information.
Passwords and access keys are obfuscated even if encryption isn’t used. The encryption option provides much stronger protection and applies to the whole config.
DBA Dash automatically creates backups of your configuration. This provides the option to rollback to a previous config if you make a mistake. These backups are now automatically cleared out after 7 days and no longer need to be removed manually. In the Options tab of the service configuration tool you can configure the retention. If retention is set to 0, config backups won’t be created.
If you enable config file encryption you might have backups of the config before you enabled encryption - potentially containing sensitive data that is not protected. The new retention policy ensures that those files do not remain indefinitely. There is a “Delete Config Backups” in the Options tab that you can use to clear out ALL config backups immediately.
See 2.41.0 release notes for a full list of fixes.