You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: