https://bugs.kde.org/show_bug.cgi?id=179678
--- Comment #85 from Bo Weaver <b...@boweaver.com> --- (In reply to Nate Graham from comment #84) > *** Bug 413360 has been marked as a duplicate of this bug. *** Well Nate here we are a year later having the same discussion. I had a feeling after updating my system when my root login failed it would lead back to this exact same cause but I did have faith you all learned from last years mistake and was hoping this wasn't going to be the exact same problem but here we are. In security after something breached we have what is called a "Lessons Learned" meeting to figure out what went wrong fix the problem and NEVER make the same mistake twice. Clearly this is not the case with developers. You did last year after about 9 months fix dolphin and kate to work as normal and I thank you for that. You even included a nice warning message on dolphin to be careful you are in root. That was all that was needed. A warning not a lock out. Again I to point out this work does NOTHING to secure the system a simple CTL ATL F1 and you can get a tty and you can log in as root. The only thing you have accomplish is keeping me from getting any work done. I want to point out something you could do to actually secure the system. These days it is hard to find a login screen that doesn't have bubbleheads with the user names and photos on it or a login box that doesn't keep the last user name in the login box. Having all the users listed on the login screen gives an attacked half the puzzle when brute forcing a password. Plus it is real ugly in an office where there are 15 users on a machine. All them bubbleheads. One thing that helps secure Linux in a brute force password attack is you have to know the user account name to run an attack. Having the name and photo of the user on the login screen gives you this information. Even Windows gives you a login screen with blank fields. So when can I have my desktop back??? -- You are receiving this mail because: You are watching all bug changes.
