Hello everyone! Here are the release notes for the most recent updates we’ve made to Duo.
You can subscribe to notifications for new release notes by following the process described here. If you have any questions about these changes, please comment below.
What’s in this release?
New and updated applications
New features, enhancements, and other improvements
Bug fixes
See all bug fixes
New and updated applications
Duo Network Gateway version 1.5.8 released
- A disabled login page will now show when the admin UI is disabled using scripted config instead of an error page.
- Bug fixes.
Duo Mobile for iOS version 3.34.0 released
- Various behind-the-scenes user experience improvements and minor bug fixes.
Duo Device Health Application for Windows 10 version 2.6.1 released
- Fixed an issue preventing Internet Explorer and some applications from communicating with the app.
- See additional enhancements related to the Device Health Application below.
Duo Authentication Proxy version 4.0.2 released
- Updated the embedded Python version to version 3.8.4, to address Python CVE-2020-1552. We urge that customers running versions 4.0.0 or 4.0.1 upgrade to version 4.0.2.
Duo Splunk Connector version 1.1.7 released
- Added support for Splunk 8.0, including the optional
python3
runtime included with Splunk 8.
- The Python runtime default in
inputs.conf
now sets the runtime to python3
for Splunk versions 8.0 or newer (python.version = python3
). This change has no effect in Splunk 7.x environments, which continue using the python2
runtime.
New features, enhancements, and other improvements
Administrator Actions Log now displays deleted activation codes
- When an administrator generates a new activation code, the old activation code is now logged in the Administrator Actions report in the Duo Admin Panel.
Improvements to the Duo Device Health Application
- Carbon Black and Sophos are now supported endpoint security agents for the Device Health Application.
Bug fixes
- Removed the ability to search by username or sort devices by number of attached users on the 2FA Devices page in order to fix slow performance when loading large lists of devices. The details page for an individual user still displays that user’s phone information.