Bandie/pam_panic
1
0
Fork 0
Code Issues 5 Pull Requests Releases Wiki Activity

Be technically right and specific

Browse Source
This commit is contained in:
Bandie
2018-11-13 17:31:03 +01:00
parent 5e5574786f
commit 90714490d1
14 changed files with 329 additions and 64 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/pam_panic/man/man8/pam_panic.8
View File

@ -122,7 +122,7 @@ This option is discouraged for security reasons.
\fBserious=\fR\fB\fIUUID\fR\fR
.RS 4
The UUID of the device containing the LUKS header to erase when the \fIpanic function\fR is triggered. Erasing the LUKS header will render the data unreadable.
The UUID of the device containing the LUKS header to erase the key slots from when the \fIpanic function\fR is triggered. Erasing the LUKS header key slots will render the data unreadable.
.PD 0
.PP
The internal command which will be executed is "\fBcryptsetup luksErase [UUID]\fR".

2
src/pam_panic_config/pam_panic_config.prebuild.sh
View File

@ -49,7 +49,7 @@ UUID_PANIC=$(N_ "Panic device chosen with UUID")
ASK_SET_PW=$(N_ "Do you want to set the passwords now?")
SET_PW_FAILED=$(N_ "Failed to set the passwords. :(")
PAM_PANICS_BEHAVIOUR=$(N_ "pam_panic's behaviour")
ASK_SERIOUS1=$(N_ "Do you wish to destroy your LUKS header in case of emergency?")
ASK_SERIOUS1=$(N_ "Do you wish to destroy your LUKS header key slots in case of emergency?")
ASK_SERIOUS2=$(N_ "This means that your encrypted root partition won't be decryptable anymore. After this question we will create a LUKS header backup, if you wish.")
MSG_SERIOUS1=$(N_ "We will destroy")
MSG_SERIOUS2=$(N_ "when you trigger the panic function.")