Fedora Account System
Red Hat Associate
Red Hat Customer
As explained in this Duo help article: https://help.duo.com/s/article/9451?language=en_US …all versions of Duo Unix before version 2.1.0 will fail to authenticate on 2026-02-02 (February 2, 2026), due to the upcoming Duo certificate authority bundle expiration. If Duo is not configured on a system to fail open, this will fail logins on that system. The version that is packaged for both Fedora and EPEL is version 1.12.1. This is an affected version, and it will fail to authenticate after 2026-02-02. (I am filing against EPEL10, but this affects all versions of Fedora and all versions of EPEL.)
BTW, I will make this offer: We use RHEL, and we use Duo as our MFA mechanism. As such, we care deeply about the Duo for Unix RPM packages (duo_unix, pam_duo), to the point where I have contributed upstream fixes: https://github.com/duosecurity/duo_unix/issues/111 https://github.com/duosecurity/duo_unix/issues/110 https://github.com/duosecurity/duo_unix/issues/164 We were building our own Duo for Unix RPM packages before they appeared in EPEL, and we have continued to use our own packages (excluding the EPEL ones) because ours are more recent. So, Davide, if you no longer use Duo, or no longer wish to maintain these packages, I would be happy to take over ownership of at least the EPEL duo_unix/pam_duo packages. We use Duo and the Duo for Unix packages extensively in our (RHEL-based) enterprise, so I am well-positioned to maintain these EPEL packages (debug issues et. al.). (We don’t use Fedora in our enterprise, but I use Fedora in my home systems. So while I would be willing to also take ownership of the Fedora packages, I am not as well positioned to debug issues there.)
Just a +1 - I'd also like to see this updated (EPEL8 and EPEL9 are of particular interest here but it needs doing across the board). Also not a Fedora user, so can't help out there - sorry!
Hi James, definitely happy to add you as a co-maintainer, thanks for the offer! What's your FAS account name? I recommend tackling Fedora first, and then we can work out updating EPEL, as we might need to do an incompatible update there (https://docs.fedoraproject.org/en-US/epel/epel-policy-updates/ is the updates policy). Happy to review PRs and assist as needed.
Hi Davide, Thanks! My FAS account name is ralston. I am hopeful that the latest version (2.2.3) won’t run afoul of the EPEL updates policy: even though the major version number changed, the package structure is the same, and the configuration file options are unchanged. (In our enterprise, we were able to move seamlessly from 1.x to 2.x, with no disruptions, with no configuration file updates needed.) Looking back over the Duo Unix release history, I think most releases would justify a new EPEL release, without running afoul of the “don’t update just because there’s a newer version” guidance in the [Packaging guidelines and policies for EPEL](https://docs.fedoraproject.org/en-US/epel/epel-policy/).
Added to the ACL, thanks! I'm mostly afk till Tue but happy to review and take a look at PRs as needed.
Working on this now, should have a package by EOD
FEDORA-2026-560ccfce04 (duo_unix-2.2.3-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-560ccfce04
FEDORA-2026-560ccfce04 (duo_unix-2.2.3-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-6a80c00ba0 (duo_unix-2.2.3-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-6a80c00ba0
FEDORA-2026-c2db75faac (duo_unix-2.2.3-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2026-c2db75faac
FEDORA-2026-6a80c00ba0 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6a80c00ba0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6a80c00ba0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-c2db75faac has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-c2db75faac` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-c2db75faac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Let's reopen this until EPEL is also updated
FEDORA-EPEL-2026-7af1bc2f16 (duo_unix-2.2.3-1.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7af1bc2f16
FEDORA-EPEL-2026-994e311e98 (duo_unix-2.2.3-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-994e311e98
FEDORA-EPEL-2026-b6a2a57e2c (duo_unix-2.2.3-1.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-b6a2a57e2c
FEDORA-EPEL-2026-eb3ade1bb6 (duo_unix-2.2.3-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-eb3ade1bb6
FEDORA-EPEL-2026-994e311e98 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-994e311e98 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-b6a2a57e2c has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-b6a2a57e2c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-7af1bc2f16 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-7af1bc2f16 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2026-eb3ade1bb6 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-eb3ade1bb6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-6a80c00ba0 (duo_unix-2.2.3-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
Hi Davide, I apologize for not getting back to this sooner. (I was under the weather, and then we had a significant snow event here in the northeastern United States). I reviewed your spec file updates, and I think everything looks good. The only potential “gotcha” was needing to explicitly add a flag to build with debugging information, and you did that. As I mentioned above, there are no changes to the configuration file syntax, or any other changes that would qualify as breaking changes. I will test out specifically the EPEL packages, and report if there are any issues. Thanks!
FEDORA-2026-c2db75faac (duo_unix-2.2.3-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-994e311e98 (duo_unix-2.2.3-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-7af1bc2f16 (duo_unix-2.2.3-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-b6a2a57e2c (duo_unix-2.2.3-1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2026-eb3ade1bb6 (duo_unix-2.2.3-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.