On Thu, 2007-02-15 at 09:27 +0000, Martin Pitt wrote: > I still need a *detailled* recipe how to reproduce this -- I tried > various combinations for half an hour without success. > > ** Changed in: sudo (Ubuntu) > Status: Confirmed => Needs Info >
I think kko answered it. When I reported the bug, I had accidentally set the date while installing ubuntu Dapper 3 days past what it should have been. The version of sudo I was using was the one that came with ubuntu 6.06 in October 2006. sudo accepts minor variations in the date, but not large ones. In my case, sudo did not have to be run when I set the date to the wrong value as it was during an installation. It might help to set up a root password and bypass sudo to set the date into the future, and then run sudo to set the date back. In addition, for some reason one of my terminal windows could use sudo successfully, but the others could not, including newly opened terminal windows. I would guess (but cannot say definitively) that this was either the window I used to set the date, or one where I has run sudo just prior to setting the date using the "time and date" menu item from the GUI. My /etc/sudoers contains the following (as far as I know, it is what comes with my ubuntu distribution): ------------------------------------ ~$ sudo cat /etc/sudoers # /etc/sudoers # # This file MUST be edited with the 'visudo' command as root. # # See the man page for details on how to write a sudoers file. # Host alias specification # User alias specification # Cmnd alias specification # Defaults Defaults !lecture,tty_tickets,!fqdn # User privilege specification root ALL=(ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL -- "sudo -k" fails when timestamp is in the future https://launchpad.net/bugs/43233 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
