Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session unlock after simulated swaylock crash #174

Closed
vulpicastor opened this issue Apr 21, 2021 · 1 comment
Closed

Session unlock after simulated swaylock crash #174

vulpicastor opened this issue Apr 21, 2021 · 1 comment

Comments

@vulpicastor
Copy link

I performed an experiment where I ran sleep 30 && pkill -9 swaylock in the terminal before locking the screen to simulate what happens if swaylock crashed. I was surprised to find that my session simply returned, unlocked.

In a similar vein to #164, is this intended behavior? Because if it is, then screenlocking under sway is no safer than the old days under Xorg.

Under the current design, is it at all possible for sway to at least terminate the user session if the screenlocker crashes? That behavior may be annoying, but at least it doesn't leave a gaping security hole.

@emersion
Copy link
Member

Yes. this is intended behaviour. You can set your lock command to swaylock || swaymsg exit if you want to quit Sway on swaylock failure.

See swaywm/wlroots#2706 for proposals to improve the status quo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants