Bug 136894 - Kdesu don't check for temporary-saved sudo password
Summary: Kdesu don't check for temporary-saved sudo password
Status: RESOLVED DUPLICATE of bug 115898
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-05 15:40 UTC by Treviño
Modified: 2010-11-06 19:09 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Treviño 2006-11-05 15:40:40 UTC
Version:           3.5.5 (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages
OS:                Linux

I'm using kubuntu edgy (KDE 3.5.5) like in previous versions, kdesu has a “bug”... Pratically it doesn't check for saved sudo password before running programs with privileged rights... If I run application Kapp with «kdesu Kapp1», then - after few secs/mins - I do «kdesu Kapp2», I get again the kdesu window asking for a su/sudo password; but now I can give it any password (or I can just leave the password field blank) and clicking on "ok" I can open the second application...
Just becouse it already know the sudo password...

Well... Couldn't it do these password check before opening kdesu window (like gtksu does)?
Something like... «If I can run Kapp2 without asking password, I'll do that; else I'll ask for password...»
It seems quite easy to say :D

More infos here: https://launchpad.net/distros/ubuntu/+source/kubuntu-default-settings/+bug/36007
Comment 1 Anton 2006-12-22 12:12:52 UTC
*** This bug has been confirmed by popular vote. ***
Comment 2 Juan Carlos Torres 2007-03-14 14:22:39 UTC
Adding my confirmation that this still happens in KDE 3.5.6.
Comment 3 Tristan Miller 2010-09-21 17:28:06 UTC
Confirming bug still exists in KDE 4.5.1.
Comment 4 Oswald Buddenhagen 2010-11-06 19:09:07 UTC

*** This bug has been marked as a duplicate of bug 115898 ***