*** This bug is a duplicate of bug 43233 ***
https://bugs.launchpad.net/bugs/43233
yes, I am also getting the same error. I thnk it has to be a bug or a
security measure. I changed my network several times and also used ssh
several times. Once I typed "sdo" instead of "sudo" for ssh. And after
*** This bug is a duplicate of bug 43233 ***
https://bugs.launchpad.net/bugs/43233
Incidentally, I just had this same problem with my old pentium II. It's
a headless server that primarily runs mpd for our music on hold. I
logged in through ssh and changed the network so that I could run apt-
*** This bug is a duplicate of bug 43233 ***
https://bugs.launchpad.net/bugs/43233
I saw the same issue on gutsy just now. I tried telling the date and
time applet to synchronize with internet servers. It couldn't find the
ntp package, but nonetheless seemed to be able to do an ntpdate call.
*** This bug is a duplicate of bug 43233 ***
https://bugs.launchpad.net/bugs/43233
** This bug has been marked a duplicate of bug 43233
"sudo -k" fails when timestamp is in the future
--
sudo: timestamp too far in the future
https://bugs.launchpad.net/bugs/76639
You received this bug noti
I think the problem may be related with DST (Daylight Saving Time). I
think, that when editing file with vi and saving it, the DST is somehow
misinterpreted and the timestamps are set to +1 hour incorrectly, which
causes the sudo error. Just a thought, but I had no problems with sudo
before editing
I can reproduce this on my 6.06.1 LTS LAMP server:
$ sudo vi /etc/network/interfaces
*I changed the IP from DHCP and added in my address, gateway and subnet
$ sudo /etc/init.d/networking restart
*Applied the changes
$ sudo vi /etc/hosts
sudo: timestamp too far in the future: Apr 21 13:07:27 2007
im opening again since im experiencing this on feisty and believe it to
be a bug.
if you manually change the time to a few hours earlier after having used
sudo you will now be unable to run any system preferences tools.
since they use gksudo e.g. network-admin will quit quietly. even if it
"only"
Only thing is, I don't have my system setup to use NTP. But, this
interesting bit showed up in the logs:
Dec 20 13:44:59 localhost ntpdate[15309]: step time server 82.211.81.145 offset
-3598.328095 sec
Dec 20 13:47:06 localhost ntpdate[15446]: step time server 82.211.81.145 offset
0.87 sec
D
Looks like this is something odd that happened with ntpdate, not sudo.
** Changed in: sudo (Ubuntu)
Status: Unconfirmed => Rejected
--
sudo: timestamp too far in the future
https://launchpad.net/bugs/76639
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Sounds like connecting to the network ran ntp via /etc/network/if-
up.d/ntpdate, causing time to be synced and set an hour or so back
(check logs?). Which would in turn be reason for sudo to complain about
timestamps being too far in the future.
Man page only specifies "Timestamps with a date grea
If you wait a little while and get closer to the timestamp, sudo starts
working, but with no password needed. I'm adding a security
vulnerability as this is unexpected behavior of a part of the security
subsystem.
** This bug has been flagged as a security issue
--
sudo: timestamp too far in the
If you reboot fsck will fix it.
Anyway I did have this bug too once...
--
sudo: timestamp too far in the future
https://launchpad.net/bugs/76639
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
12 matches
Mail list logo
