slock

commit af5084928433794ffd8f4546b333e415ff189350
parent b7dcb60995ac00886bf667f6aa63b0592fc4145f
Author: FRIGN <dev@frign.de>
Date:   Wed, 28 Sep 2016 20:20:51 +0200

Add a section on security considerations

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.

Diffstat:
M
slock.1
 | 
12
++++++++++++

1 file changed, 12 insertions(+), 0 deletions(-)
diff --git a/slock.1 b/slock.1
@@ -17,6 +17,18 @@ is executed after the screen has been locked.
 .It Fl v
 Print version information to stdout and exit.
 .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
 $
 .Nm