xsecurelock

Perhaps you'd enjoy something like the xsecurelock prompts? https://github.com/google/xsecurelock

I like the idea of showing keystrokes, but I think that a 1:1 entry has arguably better alternatives. The default entry on xsecurelock[^0] shows a character jumping on a line between keystrokes, which works well on giving key press feedback while visibly obfuscating password length, ________|_______________________ // after pressing a key it'd move around, ___________________|____________ Also, for anyone looking into preserving this last resort obfuscation behaviour you can do it with, # /etc/sudoers Defaults !pwfeedback On NixOS (using sudo-rs), security.sudo-rs.extraConfig = '' # NixOS extraConfig # =========== Defaults !pwfeedback ''; I've got to say, if you were able to see me typing, you can probably record me doing so, bug my USB keyboard, or buy a $10 wrench. I guess for people s

xsecurelock[https://github.com/google/xsecurelock] has a few variants on this.

Anyone here use https://github.com/google/xsecurelock? I found it while going through reddit.com/r/unixporn and looking at other peoples tiling window manager setups.

I used to run a very minimal desktop (cwm+rofi) what I used for screensaver was this : https://github.com/google/xsecurelock

xscreensaver + light-locker should be okay, there is no virtual keyboard. There is also xsecurelock [1] by Google. [1] https://github.com/google/xsecurelock

I'm surprised he doesn't mention XSecureLock. Its entire focus is on preventing issues like this with modularity and redundancy. https://github.com/google/xsecurelock

> that will reload it unless XSS exits with code 0 or something Sort of what https://github.com/google/xsecurelock recommends doing. Also, xsecurelock doesn't run the input and PAM auth in the same process as the lock, making input bugs (https://news.ycombinator.com/item?id=21224179) harmless as well.

Alternative for screen locking on Linux https://github.com/google/xsecurelock

When configured properly, xsecurelock does fix this type of bug. The key is to use the -l option of xss-lock, which passes a lock file descriptor to xsecurelock and waits for it to be closed before allowing the suspend. https://github.com/google/xsecurelock#automatic-locking

Linux screen lockers are somewhat notorious for security-ish bugs like that. There's a project called XSecureLock that aims to address some of those, although I'm not sure if it fixes (or can fix) the restore-ram type bug you detailed. https://github.com/google/xsecurelock

Yeah, I tried to get xsecurelock working with LXQt and systemd. What a mess. Eventually I had to just give up on it and switch back to xscreensaver-lock. I posted a thread asking for advice and did get responses, but I haven't worked up the resolve to go back and try to get it working again. Last I checked, people were just suggesting I try something else, which kind of misses the point of the activity to uses the most secure lock screen that seemed to be available. I appreciated the help, it just seems like the whole issue should be something provided by a systemd utility that you specify your lock screen for in a config file. I know people hate on it, but systemd really does tend to make it easier if you just kind of want your system fundamentals to stay in the background and just work rather than having to constantly meddle with them.

These are good suggestions, but it seems that xsecurelock still can't provide a workaround for the bug where the screen doesn't lock if a popup menu happens to be open or the pointer is grabbed in any other way [0]. I couldn't find any good way to fix this and the only suggested workaround seems to be to switch to Wayland. I've switched on all of my machines (for this and for other reasons) but please make sure you know the details of this if you still use Xorg. [0] https://github.com/google/xsecurelock#known-security-issues

I generally use videos as a screensaver, it allows me to have pretty cool screensavers fast. I use xsecurelock [0] with the saver_mplayer backend, which means that when I lock the screen, xsecurelock runs the videos in my ~/Videos directory on repeat. I couple that with something like the Iron Man schematics videos made by Territory Studio [1] and I've got myself a pretty rad looking screensaver (with minimal effort). [0] https://github.com/google/xsecurelock [1] https://www.behance.net/gallery/26009421/AVENGERS-Age-of-Ult...