Duo security pinned certificate changes

Bug #1325723 reported by psanford
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
duo-unix (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
High
Kees Cook
Saucy
Fix Released
High
Kees Cook

Bug Description

Duo Security is changing their pinned certificate on June 30, 2014 which will break any duo-unix installs on versions <= 1.9.5. More details can be found here: https://www.duosecurity.com/docs/integration_certification_upgrade. This will affect saucy, quantal, and precise releases.

SRU Justification:
Impact: duo-unix will stop working on precise and saucy without this update
Fix: updated to upstream micro releases with cert chain and SHA updates
Test: existing duo-unix configuration continues to work after update

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in duo-unix (Ubuntu):
status: New → Confirmed
Kees Cook (kees)
Changed in duo-unix (Ubuntu Precise):
status: New → In Progress
Changed in duo-unix (Ubuntu):
status: Confirmed → Fix Released
Changed in duo-unix (Ubuntu Precise):
importance: Undecided → High
assignee: nobody → Kees Cook (kees)
Kees Cook (kees)
description: updated
description: updated
Revision history for this message
Kees Cook (kees) wrote :

Upstream has release micro updates for 1.7 and 1.8, making this a much easier task.

Changed in duo-unix (Ubuntu Saucy):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Kees Cook (kees)
Revision history for this message
Kees Cook (kees) wrote :
Revision history for this message
Kees Cook (kees) wrote :
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello psanford, or anyone else affected,

Accepted duo-unix into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/duo-unix/1.8.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

description: updated
Changed in duo-unix (Ubuntu Saucy):
status: In Progress → Fix Committed
tags: added: verification-needed
Changed in duo-unix (Ubuntu Precise):
status: In Progress → Fix Committed
Revision history for this message
Brian Murray (brian-murray) wrote :

Hello psanford, or anyone else affected,

Accepted duo-unix into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/duo-unix/1.7.1-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
psanford (pms-mail) wrote :

I've tested 1.7.1-0ubuntu1 on precise. The package does work, however I can't actually functionally confirm it fixes the issue because Duo Security hasn't switched to the new root certificate yet (that won't happen until June 30, 2014).

The patch looks correct to me.

Kees Cook (kees)
tags: added: verification-done
removed: verification-needed
tags: added: verification-done-precise verification-needed
removed: verification-done
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package duo-unix - 1.7.1-0ubuntu1

---------------
duo-unix (1.7.1-0ubuntu1) precise-proposed; urgency=medium

  * New upstream micro release.
    - Fixes user-agent and certificate chain (LP: #1325723).
 -- Kees Cook <email address hidden> Wed, 11 Jun 2014 15:48:54 -0700

Changed in duo-unix (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Kees Cook (kees) wrote :

This works for me on Saucy as well. Thanks for checking precise!

tags: added: verification-done-saucy
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package duo-unix - 1.8.1-0ubuntu1

---------------
duo-unix (1.8.1-0ubuntu1) saucy-proposed; urgency=medium

  * New upstream micro release.
    - Fixes user-agent and certificate chain (LP: #1325723).
 -- Kees Cook <email address hidden> Wed, 11 Jun 2014 16:15:34 -0700

Changed in duo-unix (Ubuntu Saucy):
status: Fix Committed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote : Update Released

The verification of the Stable Release Update for duo-unix has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.