Re: [dev] [ANNOUNCE] slock-1.3

From: Carlos Torres <vlaadbrain_AT_gmail.com>
Date: Sat, 13 Feb 2016 16:01:49 -0500

you can already use xssstate to monitor the state of the screen and
the screensaver, why not use that to do both slock, and eventually
sleep?

--Carlos

On Sat, Feb 13, 2016 at 3:57 PM, hiro <23hiro_AT_gmail.com> wrote:
> Oh god no.
>
> You guys must have some strange use cases.
>
> When I run slock there's no way for me to miss whether it ran or not
> (It is pretty visible all over my screen). So I have like 1 second to
> notice this before my display shuts off for standby. In the unlikely
> event of catastrophic X-Bullshit I can just wake up my computer or
> throw it out the window and by this clear the RAM before the police
> arrives.
>
> Anyway, it would be more useful to concentrate on the password
> checking part, it segfaults commonly (which is fucking ridiculous!!)
> because ldap, linux, etc. suck.
>
> As I'm lazy I've developed a habit of using this to my advantage. When
> I get into my office I just press enter, every second time the network
> is broken (because of networkmanager) and slock segfaults while trying
> to check the password via ldap, thus i save a lot of time I'd
> otherwise waste typing my super-secure password.
>
> I would even do without *any* password, but it's company policy to screenlock.
>
> I suggest this very platform-independent alternative interface (you
> can remove special-casing for linux,bsd and such bullshit):
>
> slock < password-file
>
Received on Sat Feb 13 2016 - 22:01:49 CET