Re: [Bug 43233] Re: sudo -k fails when timestamp is in the future
On Mon, 2007-02-19 at 17:04 +, kko wrote: Martin Pitt wrote: However, I could log into a different console/pty without any problem in every case, so it never locked me out completely. Did that happen to anyone? In short, no, not to me. I believe that having the option tty_tickets in '/etc/sudoers' should prevent this from being a real possibility. (I did point out at some point that _if_ your X failed to start _and_ you only had one getty configured, you'd be in slightly more trouble. Of course, if you've modified your install this much, you know how to e.g. use a rescue disc.) It is possible to be in a situation where you can't easily use a rescue disk. To give an example, I once worked on a project at Sun Microsystems where we had to continue working over the Christmas break. I had non-refundable airline tickets, so I during the break, I was about 3000 miles away from our lab, logged in via a VPN and using VNC. We had a mix of systems, including a Linux one attached to a terminal server via a serial port. We'd use the terminal server to boot the system and get some messages when Linux crashed (we were developing a loadable kernel module). It was really important to be able to do as much as possible without physical access to the computer. Losing root access would have been a real annoyance - you might have to call someone and ask that person to drive into work to fix it. Regards, Bill -- 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
Re: [Bug 43233] Re: sudo -k fails when timestamp is in the future
On Thu, 2007-02-15 at 09:27 +, 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 rootALL=(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
Re: [Bug 43233] Re: sudo -k fails when timestamp is in the future
On Tue, 2006-12-12 at 17:00 +, Martin Pitt wrote: Apart from the fact that the warning message might be a bit scary, I don't see a problem with it. After all, it is true, and if your clock jumps, then there's definitively a problem. So what exactly do you want to change here? Sorry for not replying earlier - a filter had misfiled your email, and I'll have to fix that. Also, I was out of town for a while. The issue was not a warning message, but rather that I could not clear the time stamp so that sudo would not allow me to preform an operation after prompting for a password. There was definitely a problem with my system - I had accidentally set the date incorrectly when I installed ubuntu, used sudo, and then reset the date when I noticed the error . I had one terminal window where sudo would work, so I used that to set a root password, which allowed me to work around the problem, but avoiding the need for a root password is the main reason for using sudo. If you get the dates really messed up (typically as the result of a user error), sudo -k should simply allow you to remove the time stamp. I think what it did was to check the timestamp first because I couldn't seem to solve the problem. -- 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
