[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
>From what I can tell, you're describing the intended behavior of sudo wrt per-tty tickets. Closing as invalid. ** Changed in: sudo (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/692391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
This appears to be a side effect of trying to enforce tty_tickets properly: back in lucid for commands invoked from the menus the sudo timestamp was written under the name 'unknown'; now it does not get written at all - hence the timeout is not honored. With tty_tickets turned off, you can be prompted for password once and then any login under that id is not prompted for @timeout@ period, including ones that may be under different controlling terminal, such as a remote ssh login. But this seems to be a better workaround, than having to type in a password every 5 minutes for running synaptic. With lucid behavior, you could actually get prompted once, and then reboot the machine and not get prompted again, if the terminal name happened to match. What we really want is for timeout to be shared in a user session - a desktop session, a screen/byobu session, etc. Of course there are nested sessions: screen running in a xterm... And related ones, such as ones on the local ttys :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
After using the both the current natty sudo (1.7.4p) with !tty_tickets and the previous 1.7.2 have decided the best choice here, (for me), is to use 1.7.2p7 (w/ recent security update patch It uses tty_tickets but gives the expected behavior w/ the admin. auth. timeout and can be adjusted if wished, up or down, with an appropriate sudoers or /etc/sudoers.d/ edit Also no mouse spin on synaptic or with gksudo nautilus -(in the current natty sudo the mouse spins on for 4 -12 secs Can't see any reason to atm to build the source on natty so am using the latest package from maverick security updates. (1.7.2p7-1ubuntu2.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
Thank you Doug. That's fixed it :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
Have resolved this here by adding a line to sudoers (actually use a file in /ect/sudoers.d/ instead Defaults !tty_tickets The issue seems to be the configure option of --with-tty-tickets that was carried forward from sudo 1.7.2 but has a slightly different effect here in 1.7.4 - once the instance is closed the timeout ends Because of no response don't know if this new behavior was the new intention or just one of those things, no big deal, easily 'fixed' for those that wish the old behavior back (in lieu of some other approach Ex. here for those that wish to change in sudoers.d or if desiring to re-build sudo then just change the option in /debian/rules to --without-tty-tickets http://ubuntuforums.org/showthread.php?p=10500211#post10500211 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
** Tags added: regression ** Tags removed: running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 692391] Re: no timestamp timeout in latest sudo except for current instance
The silence is deafening in here :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/692391 Title: no timestamp timeout in latest sudo except for current instance -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
