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.
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
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
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
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
** 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
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
