Doppler On-Prem: v20.03.1
Version 20.03.1 of Doppler On-Prem has been released.
Downloads
- doppler-onprem-v20.03.1.ova
- doppler-onprem-v20.03.1.legacy.ova
- CHECKSUMS.SHA256
- CHECKSUMS.SHA256.sig
An OVA without a manifest (marked legacy
) has been provided for compatibility
with VMware administration interfaces that don’t support SHA256 checksums.
We recommend verifying the integrity of the installation images.
Changes in 20.03.1
-
(Security) Linux base images for Debian 10.3 and dependencies have been updated to the latest patch levels as of 2020-03-20.
-
(Security) A minor enumeration vulnerabilty was discovered, and fixed, in the alert system allowing for limited information exposure across groups.
-
Routers can now be permanently removed from the system via the “Remove Router” options available in the dashboard and on the router page. (#328)
-
Firmware images for Telit and Sierra Wireless modules have been updated to the latest versions. (#0276841f)
-
User management has been improved, and generates random passwords when new users are added.
-
Users can now change passwords and enable/disable two-factor authentication via the “User Profile” menu option. (#268)
-
Default route is now searchable in the dashboard via the
def_route:
keyword (#308) -
A bug was fixed on the router page, where the rtask list did not show up properly (#9cdc96ae).
-
A bug was fixed in the login system where the system would return a server error if a users session was expired in some cases.
-
A bug was fixed in the audit log where links to routers were incorrect under some circumstances. (#310)
-
A bug has been fixed in the dashboard selection mechanism preventing a crash if a router becomes unavailable to the user due to a group change. (#569efdeb)
-
A bug was fixed in scheduled tasks where a temporary failure could trigger an immediate retry causing resource exhaustion. (#dd8d45a5)
-
The default memory size for the OVA package has been increased from 8GB to 10GB to help with performance and stability under load.
NOTE: A database schema change is required for this update. It can be be
performed during the upgrade using the update-database
command in the CLI,
after net
and db
has been configured.