It is clear we are not going to divert from upstream on this. Marking
"Won't Fix".
** Changed in: sudo (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2858
Would it be appropriate to close this bug as "Won't Fix" since this is
not really a security issue and we won't diverge from upstream?
--
Local privilege escalation when executed with nohup
https://bugs.launchpad.net/bugs/285805
You received this bug notification because you are a member of Ubunt
** Changed in: sudo (Ubuntu)
Importance: Medium => Low
Status: Incomplete => Confirmed
--
Local privilege escalation when executed with nohup
https://bugs.launchpad.net/bugs/285805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue is that the behavior of sudo changed in Hardy when running
sudo under nohup. '-k/-K' won't invalidate/remove the
/var/run/sudo//unknown (aka "nohup PTY") entry unless run
under nohup. Gutsy and earlier didn't seem to have a concept of a "nohup
PTY", so this is confusing for users who expe
If the issue is just that sudo -k doesn't also delete the ticket for the
"nohup PTY", then this is indeed a dupe of bug 269992.
** Changed in: sudo (Ubuntu)
Status: Triaged => Incomplete
--
Local privilege escalation when executed with nohup
https://bugs.launchpad.net/bugs/285805
You rece
$ nohup sudo touch foo
nohup: ignoring input and appending output to `nohup.out'
[sudo] password for martin:
sudo uses direct tty input instead of reading from stdin. So if the user
doesn't already have a TTY ticket, this works as expected.
If I already have a TTY ticket, this still works, becau
"However, the importance is best at Medium or even Low IMO because this
does not subvert sudo protections (ie, you need to be allowed to perform
the action in sudoers)"
Jamie - Thats what I meant to say when I said you have to be in the
admin group.
I lowered the importance once I realised that y
You do not have to be in the admin group to 'exploit' it. However, the
importance is best at Medium or even Low IMO because this does not
subvert sudo protections (ie, you need to be allowed to perform the
action in sudoers). Also, the timestamp feature does work (ie, you'll be
prompted for a passw
Downgrading the importance actually, as it seems you have to be in the
admin group to exploit it
** Summary changed:
- deleting sudo timestamp is non-intuitive when run under nohup
+ Local privilege escalation when executed with nohup
** Changed in: sudo (Ubuntu)
Importance: Critical => Mediu