public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: escape from i3lock
Date: Fri, 12 Jul 2019 02:11:35 +0200	[thread overview]
Message-ID: <20190712001135.g7ziilwhkxoo7slx@grusum.endjinn.de> (raw)
In-Reply-To: <2e7820e8c6ef5aaa4e0b7852a66b873ad1915452.camel@openeye.net>

Hello,

On Thu, 11 Jul 2019, Laurence Perkins wrote:
>You could also leave DontVTSwitch on all the time and set a keyboard
>shortcut to run chvt (man 1 chvt) with appropriate permissions and
>parameters instead.  Keyboard shortcuts shouldn't get processed if the
>screen is locked.

The screensaver has to get _and keep_ the lock on input.

The sad thing is, people do needless rewrites and get it wrong again
and again and again, despite jwz' xscreensaver code from 1991 on,
setting an example on how to do it right... Cue gnome-screensaver, the
kde stuff, apparently also i3lock etc.pp. ad nauseam, all repeating
the very bugs jwz wrote about in 2004 (the toolkits.html)...

VT Switching is just a little subclass of the underlying problems of
those "lock screen" programs that don't lock your screen.

==== https://www.jwz.org/xscreensaver/toolkits.html / Epilogue ====
I wrote this document in 2004, explaining the approach to privilege
separation that xscreensaver has taken since 1991. Of course, the
people doing needless rewrites of xscreensaver have ignored it for
that whole time, and have then gone on to introduce exactly the bug
that I described in this document as a hypothetical strawman! And --
this would be hilarious if it weren't so sad -- have introduced it
multiple times. As I said in 2015:

    If you are not running xscreensaver on Linux, then it is safe to
    assume that your screen does not lock. Once is happenstance. Twice
    is coincidence. Three times is enemy action. Four times is
    Official GNOME Policy.
====
(read the whole thing linked document!). Also:

https://www.jwz.org/xscreensaver/man1.html#8
https://www.jwz.org/blog/2014/04/the-awful-thing-about-getting-it-right-the-first-time-is-that-nobody-realizes-how-hard-it-was/
https://www.jwz.org/blog/2015/04/i-told-you-so-again/
(also follow the "previous" links ;)

So the solution is to just use "xscreensaver" by jwz. Which can be
configured to just blank the screen etc. as wanted by the op. See also
the FAQ: https://www.jwz.org/xscreensaver/faq.html

HTH,
-dnh

-- 
"Humans need fantasy .. to *be* human"     -- Death (in Hogfather)


  reply	other threads:[~2019-07-12  0:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 17:03 [gentoo-user] escape from i3lock Ian Zimmerman
2019-07-10 18:44 ` François-Xavier CARTON
2019-07-10 22:48   ` [gentoo-user] " Ian Zimmerman
2019-07-10 23:21     ` artur.tamm.85
2019-07-10 23:46     ` artur.tamm.85
2019-07-11 16:57       ` Ian Zimmerman
2019-07-11 20:47         ` Ian Zimmerman
2019-07-11 21:01           ` artur.tamm.85
2019-07-11 21:10             ` Laurence Perkins
2019-07-12  0:11               ` David Haller [this message]
2019-07-12  1:17                 ` Laurence Perkins
2019-07-12  8:48                   ` Michele Alzetta
2019-07-11  0:43     ` Adam Carter
2019-07-11 16:49       ` Ian Zimmerman
2019-07-11 20:28   ` Nuno Silva
2019-07-12 16:01     ` Ian Zimmerman
2019-07-12 16:05       ` Michele Alzetta
2019-07-12 16:09       ` Laurence Perkins
2019-07-13 19:11       ` Nuno Silva
2019-07-10 19:23 ` [gentoo-user] " Alec Ten Harmsel
2019-07-10 20:52   ` Neil Bothwick
2019-07-10 21:00     ` Alec Ten Harmsel
2019-07-10 22:45   ` [gentoo-user] " Ian Zimmerman
2019-07-10 21:18 ` [gentoo-user] " Francesco Turco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190712001135.g7ziilwhkxoo7slx@grusum.endjinn.de \
    --to=gentoo@dhaller.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox