remove support for running post lock command
This command was used for example to suspend-to-ram (man page example). On Linux running this command inherits OOM killer immunity. This could be abused by an other local user on the same machine (abusing resources). To keep the use-case for suspend-to-ram an user could write a wrapper script for it, outside the scope of slock. Simplify argument handling, because the post-lock command parameter is removed. Reported by: Acts1631 <acts1631kjv@proton.me>
This commit is contained in:
1 parent
890eaf6343
commit
65cb721c9e
4 files changed
+7
-95
No files matched your search
@@ -1,4 +1,4 @@
|
||||
.Dd October 6, 2023
|
||||
.Dd September 5, 2026
|
||||
.Dt SLOCK 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@@ -7,14 +7,9 @@
|
||||
.Sh SYNOPSIS
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Ar cmd Op Ar arg ...
|
||||
.Sh DESCRIPTION
|
||||
.Nm
|
||||
is a simple X screen locker.
|
||||
If provided,
|
||||
.Ar cmd
|
||||
is executed after the screen has been locked.
|
||||
.Pp
|
||||
The options are as follows:
|
||||
.Bl -tag -width Ds
|
||||
.It Fl v
|
||||
@@ -22,10 +17,6 @@ Print version information to stdout and exit.
|
||||
.El
|
||||
.Sh EXIT STATUS
|
||||
.Ex -std
|
||||
.Sh EXAMPLES
|
||||
$
|
||||
.Nm
|
||||
/usr/sbin/s2ram
|
||||
.Sh SECURITY CONSIDERATIONS
|
||||
To make sure a locked screen can not be bypassed by switching VTs
|
||||
or killing the X server with Ctrl+Alt+Backspace, it is recommended
|
||||
|
||||
Reference in new issue
Block a user