[Bug 229336] New: screen locked by kde screensaver cannot be unlocked by root
https://bugzilla.novell.com/show_bug.cgi?id=229336 Summary: screen locked by kde screensaver cannot be unlocked by root Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: mhopf@novell.com QAContact: qa@suse.de The KDE screensaver does not allow unlocking by user root and the root password. This is especially annoying, if the logged in user doesn't have a valid pwd entry in a new environment (laptop, moved from one NIS zone to another). As the screensaver specifically points the user at killing it directly (even prints out the pid), this is no security issue at all. It's just a matter of convenience, whether root has to login into a console and to kill the process manually, or can just unlock the screen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 stbinner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement ------- Comment #1 from stbinner@novell.com 2006-12-18 08:41 MST ------- Arguable enhancement: Reading other report like bug 186204 it seems to considered a fault if enabled by default. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #2 from mhopf@novell.com 2006-12-18 08:57 MST ------- WTF?!? root can *always* log into a machine (as long as runlevel 5 has gettys running) and kill the screensaver. This gives a false sense of security, and is thus IMHO even contra productive. Also this is about KDE and not Gnome, in contrast to the mentioned bug report. I also couldn't find an option in the control center to change the behavior. But of course I might have overlooked it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #3 from stbinner@novell.com 2006-12-21 03:04 MST -------
This gives a false sense of security, and is thus IMHO even contra productive.
About security, you must have a really bad admin (which teachs you) to enter the root password into everything that looks like a screensaver (prompt). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #4 from mhopf@novell.com 2007-01-02 09:54 MST ------- (In reply to comment #3)
About security, you must have a really bad admin (which teaches you) to enter the root password into everything that looks like a screensaver (prompt).
You're not really thinking before making these accusations?!? With almost 10 years of security experience (5+ years as admin, building up a completely new infrastructure at the University for my Professor and only a single break-in due to a *very* bad password and wrong access rights of a different user, who subsequently typed in the root password) I think I know a bit about this topic. Still learning, of course. Don't tell me this type of user shouldn't have the root pwd, I know that myself (it's never the admin who makes the policy...). By prohibiting killing the screensaver with the root password you gain nothing. Nada. Zero. I already typed it in, so if this was the screensaver of a bad guy it would have been captured anyway. But this is about a completely different issue. It's just much more convenient, to kill the screensaver with the root password if the PAM module cannot authenticate you any more (network doesn't work any longer after suspend, so NIS doesn't know you any longer). I'm talking about my personal workstation and laptops, where I started the locking program myself. It's also much more convenient to be able to remove the screen saver without locking into another computer (here where everybody knows the root password) if you absolutely need to access a computer. Hell, you would log into the computer with the root password anyway. It's a different issue in an environment with untrusted users, of course. There you should never type in the root password in an unsafe environment, but under linux we almost by definition don't have something like that. Windows has Ctrl-Alt-Del for that (which is captured by the kernel), but Linux doesn't have an equivalent. So anybody could fake the login screen and capture the root password. This is no different to a "personalized" screen locker. By the way - the proposed behavior (being able to kill with root pwd) is also the default behavior of both xlock and xscreensaver... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #5 from mhopf@novell.com 2007-01-02 09:57 MST ------- (In reply to comment #4)
It's a different issue in an environment with untrusted users, of course. There you should never type in the root password in an unsafe environment, but under linux we almost by definition don't have something like that. Windows has
I forgot to mention that this is a restriction that can only be placed by the admin on *himself*. No "feature" can hinder the admin from entering the root pwd in bad places. This is social security only. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |security-team@suse.de ------- Comment #6 from coolo@novell.com 2007-01-10 02:22 MST ------- Just to clarify the obvious: would this change be fine with the security team? I'd like to know _before_ we spend time on it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|security-team@suse.de | Resolution| |WONTFIX ------- Comment #7 from coolo@novell.com 2007-01-10 02:25 MST ------- http://bugs.kde.org/show_bug.cgi?id=45980 - long living feature request, 3 votes so far. Doesn't seem to be interesting for most -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #8 from meissner@novell.com 2007-01-10 02:56 MST ------- in general this is a longstanding issue also on the GNOME/xscreensaver side. Some people want it, some people hate it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #9 from lnussel@novell.com 2007-01-12 03:40 MST ------- Maybe with some additional button that starts a new pam conversation for root on request. The common method of starting a hidden pam conversation and trying to insert what has been typed before is broken IMO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=229336 ------- Comment #10 from coolo@novell.com 2007-01-12 06:18 MST ------- A "Try as root" button in the "Password failed" message box? I'm not sure this is easily possible. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com