2018-03-28 02:34:52 +00:00
'\" t
. \" Title: pam_panic
. \" Author: [see the "AUTHORS" section]
. \" Date: 2018-03-26
. \" Manual: Linux-PAM Panic Manual
. \" Source: Linux-PAM Panic Manual
. \" Language: English
. \"
.TH "PAM_PANIC" "8" "2018-03-26" "PAM Panic Manual" "PAM Panic Manual"
.ie \n (.g .ds Aq \(aq
.el .ds Aq '
. \" -----------------------------------------------------------------
. \" * set default formatting
. \" -----------------------------------------------------------------
. \" disable hyphenation
.nh
. \" disable justification (adjust text to left margin only)
.ad l
. \" -----------------------------------------------------------------
. \" * MAIN CONTENT STARTS HERE *
. \" -----------------------------------------------------------------
.SH "NAME"
2018-03-28 03:07:39 +00:00
pam_panic \- PAM module for access control using removable media (with panic function)
2018-03-28 02:34:52 +00:00
.SH "SYNOPSIS"
.HP \w '\fBpam_panic\&.so\fR\ 'u
\fB pam_panic\& .so\fR [allow=\fI UUID(GPT)\fR ] [reject=\fI UUID(GPT)\fR ] [reboot] [poweroff] [serious=\fI UUID\fR ]
.SH "DESCRIPTION"
.PP
2018-03-28 03:07:39 +00:00
The pam_panic PAM module protects sensitive data and provides a panic function for emergency situations\& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
There are two removable media which work as keys: the auth key and the panic key\& . The auth key will let you pass to the password prompt whereas the panic key, if provided, will securely erase the LUKS header, rendering the data unreadable\& .
2018-03-28 02:34:52 +00:00
.SH "OPTIONS"
.PP
\fB allow=\fR \fB \fI UUID(GPT)\fR \fR (required)
.RS 4
2018-03-28 03:07:39 +00:00
The UUID of the device to be used for authentication (the auth key)\& .
2018-03-28 02:34:52 +00:00
.PD 0
.PP
.PD 1
2018-03-28 03:48:13 +00:00
The device must have a GPT-formatted device with at least one partition on it\& .
The UUID of a GPT-formatted device looks like "12345678-9ABC-DEF0-1234-56789ABCDEF0"\& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
See \fB HOW TO DETERMINE MY UUIDS\fR for details\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
\fB reject=\fR \fB \fI UUID(GPT)\fR \fR (required)
.RS 4
2018-03-28 03:07:39 +00:00
The UUID of the device to be used in emergencies. The presence of this device will trigger \fB reboot\fR , \fB poweroff\fR and/or the panic function, depending on whether \fB reboot\fB , \fB poweroff\fB , and/or \fB serious\fB are specified.
2018-03-28 02:34:52 +00:00
.PD 0
.PP
.PD 1
2018-03-28 03:48:13 +00:00
The device must have a GPT-formatted device with at least one partition on it\& .
The UUID of a GPT-formatted device looks like "12345678-9ABC-DEF0-1234-56789ABCDEF0"\& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
See \fB HOW TO DETERMINE MY UUIDS\fR for details\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
\fB reboot\fR (recommended)
.RS 4
2018-03-28 03:07:39 +00:00
Indicates that the system should reboot upon encountering the device specified with \fB reject\fR \& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
If \fB poweroff\fR is also specified, \fB reboot\fR will be ignored\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
\fB poweroff\fR
.RS 4
2018-03-28 03:07:39 +00:00
Indicates that the system should shut down upon encountering the device specified with \fB reject\fR \& .
This option is discouraged for security reasons\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
\fB serious=\fR \fB \fI UUID\fR \fR
.RS 4
2018-03-28 03:07:39 +00:00
The UUID of the device containing the LUKS header to erase upon encountering the device specified with \fB reject\fR \& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
NOTE: You should make a backup of the LUKS header before using this function\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
2018-03-28 03:07:39 +00:00
.SH "USAGE"
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
To activate the module you have to configure PAM\& . See \fB pam\& .conf(5)\fR for details\& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
In general, you will want to add the following to the top of a PAM configuration file:
2018-03-28 02:34:52 +00:00
.PD 0
.RS 4
2018-03-28 03:07:39 +00:00
auth requisite pam_panic\& .so auth=<UUID> reject=<UUID> reboot serious=<UUID>
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
account requisite pam_panic\& .so
2018-03-28 02:34:52 +00:00
.RE
.PD 1
.SH "HOW TO DETERMINE MY UUIDS"
.PP
You will find your UUIDs in \fI /dev/disk/by-partuuid\fR \& .
You might want to execute "\fB ls -l /dev/disk/by-partuuid/\fR " in your favourite shell to find out which UUID is which device\& .
.SH "RETURN VALUES"
.PP
PAM_SUCCESS
.RS 4
Access was granted\& .
.RE
.PP
PAM_IGNORE
.RS 4
2018-03-28 03:07:39 +00:00
An error has occured\& . The module will be ignored.\& .
2018-03-28 02:34:52 +00:00
.RE
.PP
PAM_MAXTRIES
.RS 4
2018-03-28 03:07:39 +00:00
The removable media was not detected\& .
2018-03-28 02:34:52 +00:00
.RE
.SH "FILES"
.PP
/lib/*/security/pam_panic\& .so
.RS 4
2018-03-28 03:38:47 +00:00
This PAM module\& .
2018-03-28 02:34:52 +00:00
.RE
.SH "BUGS"
.PP
2018-03-28 03:07:39 +00:00
Please report bugs and send pull requests to <https://github\& .com/Bandie/pam_panic>\& .
2018-03-28 02:34:52 +00:00
.SH "SEE ALSO"
.PP
2018-03-28 03:07:39 +00:00
\fB cryptsetup\fR (8), \fB pam\fR (8), \fB pam\& .conf\fR (5)
2018-03-28 02:34:52 +00:00
.SH "AUTHORS"
.PD 0
.PP
2018-03-28 03:07:39 +00:00
pam_panic was written by Bandie <bandie@chaospott\& .de>\& .
2018-03-28 02:34:52 +00:00
.PP
2018-03-28 03:07:39 +00:00
This man page has been revised by Jordy Dickinson <jordy\& .dickinson@icloud\& .com>