Hello. I'm still on Kubuntu Dapper, I don't know what you are using. (My sudo package is version "1.6.8p12-1ubuntu6", and "sudo -v" gives, accordingly, "Sudo version 1.6.8p12".)
Here's what I just used for reproducing this:
0) Boot up.
1) Do "ctrl-alt-f1" and login on tty1 as yourself.
2) "sudo date -s xx:yy:zz" where xx:yy:zz is at least two hours in the future (I used "14:00:00")
3) "sudo date -s aa:bb:cc" where aa:bb:cc is two hours and ten minutes less than xx:yy:zz (I used "11:50:00")
4) "sudo -k"
5) "sudo -K"
6) "sudo -v"
7) "sudo ls"
Parts 4 through 7 give the same error, timestamp too far in the future.
Re-browsing the discussion above, I feel it necessary to add that _none_ of the commands 4 through 7 give me the opportunity to input my password. If I read you correctly, it does for you, Martin. For this reason I am beginning to suspect differences in how sudo is configured for causing this. I will attach my "/etc/sudoers", though I believe it is the standard one shipped with Dapper.
(Now, here's a hint that something _may_ be amiss and possibly even depend on the individual system. If I was observing closely enough, on the very first time I tried this today, "sudo -k" wouldn't work, but "sudo -K" immediately after that did. I used much the same procedure as above, but not the same times by the second etc. I'm sorry that I can't confirm this to 100%, since I don't have a videographic memory... If this really was happening, though, it would seem possible that the program unintentionally used some random bit in the memory for identifying what to do.)
Hello. I'm still on Kubuntu Dapper, I don't know what you are using. (My sudo package is version "1.6.8p12- 1ubuntu6" , and "sudo -v" gives, accordingly, "Sudo version 1.6.8p12".)
Here's what I just used for reproducing this:
0) Boot up.
1) Do "ctrl-alt-f1" and login on tty1 as yourself.
2) "sudo date -s xx:yy:zz" where xx:yy:zz is at least two hours in the future (I used "14:00:00")
3) "sudo date -s aa:bb:cc" where aa:bb:cc is two hours and ten minutes less than xx:yy:zz (I used "11:50:00")
4) "sudo -k"
5) "sudo -K"
6) "sudo -v"
7) "sudo ls"
Parts 4 through 7 give the same error, timestamp too far in the future.
Re-browsing the discussion above, I feel it necessary to add that _none_ of the commands 4 through 7 give me the opportunity to input my password. If I read you correctly, it does for you, Martin. For this reason I am beginning to suspect differences in how sudo is configured for causing this. I will attach my "/etc/sudoers", though I believe it is the standard one shipped with Dapper.
(Now, here's a hint that something _may_ be amiss and possibly even depend on the individual system. If I was observing closely enough, on the very first time I tried this today, "sudo -k" wouldn't work, but "sudo -K" immediately after that did. I used much the same procedure as above, but not the same times by the second etc. I'm sorry that I can't confirm this to 100%, since I don't have a videographic memory... If this really was happening, though, it would seem possible that the program unintentionally used some random bit in the memory for identifying what to do.)