Bug#478274: What about fixing this bug?
Eric Valette wrote: > Eric Valette wrote: >> Sune Vuorela wrote: >>> On Tue, 24 Jun 2008 12:58:25 +0200, Eric Valette <[EMAIL PROTECTED]> >>> wrote: Can annyone care to fix real bug ;-) >>> Sorry. We are too busy with closing all your non-bugs. >> You bloody arrogant idiot! No being able to login once the automtic >> screen saver start and asks for a password is not a bug? You have to >> become root and kill the process. Not really safe in a business environment! > > And BTW the same bug cause the same problem with LDAP user management if > you think NIS is just too old. And the answer was just the same: who > cares for non corparate environment. > > Bug was #298148. In addition, you should probably read kcheckpass man page before saying it was not intended to be setuid root: KCheckPass is KDE's authentication program. It is meant to be used by any software in need of user authentication, most notably screensavers. It enhances security be the following means: - It's only a small program, which is hopefully simple enough to allow it to be SUID root. Setting it to SUID root is necessary on Shadow Password systems. - No other program in need of user authentication, must be SUID root. - It provides a single implementation to check passwords. So one only must take a closer look at KCheckPass to ensure password security. It's much easier for programs using KCheckPass to preserve security. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478274: What about fixing this bug?
Eric Valette wrote: > Sune Vuorela wrote: >> >> On Tue, 24 Jun 2008 12:58:25 +0200, Eric Valette <[EMAIL PROTECTED]> >> wrote: >>> Can annyone care to fix real bug ;-) >> Sorry. We are too busy with closing all your non-bugs. > > You bloody arrogant idiot! No being able to login once the automtic > screen saver start and asks for a password is not a bug? You have to > become root and kill the process. Not really safe in a business environment! And BTW the same bug cause the same problem with LDAP user management if you think NIS is just too old. And the answer was just the same: who cares for non corparate environment. Bug was #298148. -- eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478274: What about fixing this bug?
Sune Vuorela wrote: > > > On Tue, 24 Jun 2008 12:58:25 +0200, Eric Valette <[EMAIL PROTECTED]> > wrote: >> Can annyone care to fix real bug ;-) > > Sorry. We are too busy with closing all your non-bugs. You bloody arrogant idiot! No being able to login once the automtic screen saver start and asks for a password is not a bug? You have to become root and kill the process. Not really safe in a business environment! > And you by the way missed to tell what binary you meant to be setuid root. For someone as intelligent as you are, it should be obvious. > > But anyways, no matter which binary it is, documenting it in a README file > that you might want to add setuid root (with dpkg-statoverride) to that > specific file if you use NIS will be the fix. Fair enough. But someone else may reopen the bug then. Automating nis discovery would be more wyse and evident for you superman ;-) > > As it works without problems in non-nis-environments, there is no reason to > make it setuid root for all users. I disagree. Its is obvious that you have no clue of what using linux in a corporate environment means. -- eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478274: What about fixing this bug?
On Tue, 24 Jun 2008 12:58:25 +0200, Eric Valette <[EMAIL PROTECTED]> wrote: > Can annyone care to fix real bug ;-) Sorry. We are too busy with closing all your non-bugs. And you by the way missed to tell what binary you meant to be setuid root. But anyways, no matter which binary it is, documenting it in a README file that you might want to add setuid root (with dpkg-statoverride) to that specific file if you use NIS will be the fix. As it works without problems in non-nis-environments, there is no reason to make it setuid root for all users. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#478274: What about fixing this bug?
Can annyone care to fix real bug ;-) -- eric -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
