Bug 391406

Summary: Bug or no bug?
Product: [Unmaintained] kscreenlocker Reporter: Andres Betts <anditosan1000>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: bshah, kde, mgraesslin
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: NetBSD   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Andres Betts 2018-03-05 00:59:24 UTC 
Kscreenlocker can be disabled by pressing any button or moving the mouse as soon as it appears. In my mind, if the screen is locked, it should not be unlocked by any means. This could be a security problem. If I walk away from my computer, thinking that it will lock, but as soon as the flash comes on the screen, someone presses a button, then they have access.

The current default settings show that the computer lock will start after 5 minutes and will take 5 seconds to enter your password.

Not sure if this is by design. But would propose that there should be no way that you can disable Kscreenlocker unless you use your computer password.

Here is a video of the behavior.

https://youtu.be/3AuvvFaCk6c

Thank you,

Andy
Comment 1 Martin Flöser 2018-03-05 05:24:19 UTC 
Of course this is by design and a common and important feature.
Comment 2 Christoph Feck 2018-03-05 11:45:22 UTC 
> Kscreenlocker can be disabled by pressing any button or moving the mouse

This of course should never happen. Which distribution are you using?
Comment 3 Andres Betts 2018-03-05 15:10:03 UTC 
Neon
Comment 4 Kai Uwe Broulik 2018-03-05 16:02:06 UTC 
> This of course should never happen.

When it automatically locks the screen you can unlock it by user interaction within the first couple of seconds (ninja mouse move) to prevent it from locking when you just let your computer sit idle whilst busy elsewhere. This is by design and fine. (I was wondering whether the password field is actually grayed out during that period?)
Comment 5 Christoph Feck 2018-03-06 02:38:43 UTC 
Ah, okey. I probably interpreted the "lock will start after 5 minutes" wrong.