Package: sudo Version: 1.6.8p12-4 Severity: normal I just realised my clock was set to UTC rather than UTC+1 as it should be, so I fixed it.
Now, when I try to use 'sudo' I see: sudo: timestamp too far in the future: Dec 22 17:44:47 2006 That's fair enough - the last time I used sudo the clock was set wrongly. So I can wait an hour, and then sudo will start working for me again. But I should be able to run "sudo -k" or "sudo -K" to delete the timestamp file, but I can't: $ type sudo sudo is hashed (/usr/bin/sudo) $ sudo -k sudo: timestamp too far in the future: Dec 22 17:44:47 2006 $ sudo -K sudo: timestamp too far in the future: Dec 22 17:44:47 2006 $ The man page says that neither -k not -K require a password, so why is the timestamp file being checked for these cases? -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sudo depends on: ii libc6 2.3.6.ds1-9 GNU C Library: Shared libraries ii libpam-modules 0.79-4 Pluggable Authentication Modules f ii libpam0g 0.79-4 Pluggable Authentication Modules l sudo recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
