Martin Pitt: Obviously, if there is a problem (with something that causes the clock to jump), the user probably needs to be able to use root capabilities (e.g. 'sudo') to rectify the problem. For this, resetting the timestamp is what is often needed, as indicated by these reports.
As I stated in a previous comment, it is a good thing that normal 'sudo' commands without the '-k' or '-K' switches do fail if the timestamp is too far in the future. This serves the purpose of alerting the user to the fact that something is amiss. However, when the user then starts to rectify the problem, it really doesn't help if 'sudo -k' or 'sudo -K' don't work as stated in 'man sudo'. In sum, if the user has to find a workaround (as indicated here) to be able to tackle the problem, it seems to me that the user has to jump through unnecessary hoops. (Akkana Peck: Adapting the man pages to reflect current limitations would be a bad option, in my opinion - I'm sure you agree, though. The commands 'sudo -k' and 'sudo -K' do normally work, cleaning the timestamp as stated and thus forcing the password request for next usage of 'sudo', just as long as this bug doesn't prevent this from happening.) -- "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
