Comment 3 for bug 706045

It appears that the latest merge of sudo dropped the required patch

sudo (1.7.4p4-5ubuntu1) natty; urgency=low

  * Merge from debian unstable (LP: #689025), remaining changes:
    - debian/rules:
      + compile with --without-lecture --with-tty-tickets (Ubuntu specific)
      + install man/man8/sudo_root.8 (Ubuntu specific)
      + install apport hooks
    - debian/sudo-ldap.dirs, debian/sudo.dirs: add
      usr/share/apport/package-hooks
  * This upload also fixes: LP: #609645

 -- Lorenzo De Liso <email address hidden> Wed, 15 Dec 2010 21:32:57 +0100

sudo (1.7.4p4-5) unstable; urgency=low
sudo (1.7.4p4-4) unstable; urgency=low
sudo (1.7.4p4-3) unstable; urgency=low
sudo (1.7.4p4-2) unstable; urgency=low
sudo (1.7.4p4-1) unstable; urgency=high
sudo (1.7.2p7-1ubuntu3) natty; urgency=low
sudo (1.7.2p7-1ubuntu2) maverick; urgency=low

sudo (1.7.2p7-1ubuntu1) maverick; urgency=low

  * Merge from debian unstable. Remaining changes:
   - debian/rules:
     - compile with --without-lecture --with-tty-tickets (Ubuntu specific)
     - install man/man8/sudo_root.8 (Ubuntu specific)
     - install apport hooks
   - debian/sudo-ldap.dirs, debian/sudo.dirs: add
     usr/share/apport/package-hooks
   - debian/patches/ubuntu-sudo-as-admin-successful.patch: adjust sudo.c so
     that if the user successfully authenticated and he is in the 'admin'
     group, then create a stamp ~/.sudo_as_admin_successful. Our default bash
     profile checks for this and displays a short intro about sudo if the flag
     is not present
  * Dropped the following, now included upstream:
    - fix for CVE-2010-1163
    - fix for CVE-2010-0426
    - debian/sudo.postinst, debian/sudo-ldap.postinst: update description to
      match behavior in sudoers file
    - don't install init script. Debian moved to /var/lib/sudo from
      /var/run/sudo, so Ubuntu's tmpfs usage won't clean those out
      automatically any more, so we now need the initscript.

 -- Jamie Strandboge <email address hidden> Tue, 06 Jul 2010 11:43:05 -0500

None of the intervening changelog entries mention dropping the patch, so guessing it was dropped in error?