suckless/slock
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add a section on security considerations

Browse source 
The section on security considerations sheds some light on the problems that we
can't solve within slock but which the user has to solve in his X configuration.
This commit is contained in:
FRIGN 2016-09-28 20:20:51 +02:00 committed by Markus Teich
parent 2d85c5baed
commit bd069b08c5
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
slock.1
View file

@ -17,6 +17,18 @@ is executed after the screen has been locked.
.It Fl v .It Fl v
Print version information to stdout and exit. Print version information to stdout and exit.
.El .El
.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
to disable both in
.Xr xorg.conf 5
for maximum security:
.Bd -literal -offset left
Section "ServerFlags"
Option "DontVTSwitch" "True"
Option "DontZap" "True"
EndSection
.Ed
.Sh EXAMPLES .Sh EXAMPLES
$ $
.Nm .Nm