2018-04-01 23:18:29 +00:00
[](https://travis-ci.org/pampanic/pam_panic)
2018-04-01 23:16:41 +00:00
[](https://app.codacy.com/app/pampanic/pam_panic?utm_source=github.com& utm_medium=referral& utm_content=pampanic/pam_panic& utm_campaign=badger)
2018-04-01 23:18:29 +00:00
# pam\_panic
2018-03-29 02:38:48 +00:00
2018-03-27 01:32:29 +00:00
## Purpose
2018-04-01 00:31:27 +00:00
pam\_panic is a PAM module that protects sensitive data and provides a panic function for emergency situations.
2018-03-27 01:32:29 +00:00
2018-03-31 23:53:41 +00:00
2018-03-27 02:20:16 +00:00
## How it works
2018-03-31 23:53:41 +00:00
You can choose one of two options:
### Using two removable media
2018-03-28 19:42:14 +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-27 01:32:29 +00:00
2018-03-31 23:53:41 +00:00
### Using two passwords previous your own password
There are two passwords you are able to set: the key password and the panic password. The key password will let you pass to the original password prompt whereas the panic password, if provided, will securely erase the LUKS header, rendering the data unreadable.
2018-03-27 01:32:29 +00:00
## Installation
2018-03-28 19:42:14 +00:00
You will need GCC or similar, as well as the PAM headers. Some distributions package the PAM headers as `libpam0g-dev` .
To compile and install it, do the following within the project's root directory:
2018-03-27 01:32:29 +00:00
```
make
sudo make install
```
2018-03-28 19:42:14 +00:00
Note: the paths of the `reboot` , `poweroff` , and `cryptsetup` commands are passed to the module at compile-time.
2018-03-27 01:32:29 +00:00
## Preparation
2018-03-31 23:53:41 +00:00
In that case you want to use removable media:
2018-03-28 19:42:14 +00:00
You'll need two GPT-formatted removable storage devices, and said devices must have at least one partition. Here's an example `fdisk` session, showing how this might be accomplished:
2018-03-27 01:32:29 +00:00
```
$ sudo fdisk /dev/sdc
Welcome to fdisk (util-linux 2.31.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): g
Created a new GPT disklabel (GUID: AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA).
Command (m for help): n
Partition number (1-128, default 1):
First sector (2048-15661022, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-15661022, default 15661022):
Created a new partition 1 of type 'Linux filesystem' and of size 7.5 GiB.
Command (m for help): w
```
2018-03-27 13:52:32 +00:00
You'll find the UUID of your partition in `/dev/disk/by-partuuid/` . You can find out which device is which typing `ls -l /dev/disk/by-partuuid/` in your favourite shell.
2018-03-27 01:32:29 +00:00
2018-03-28 19:42:14 +00:00
## Configuration
2018-03-31 23:53:41 +00:00
To configure the module, add the following to the appropriate PAM configuration file(s): (see pam.conf(5) for details on these files).
2018-03-27 01:32:29 +00:00
2018-03-31 23:53:41 +00:00
### Using the removable media:
2018-03-27 01:32:29 +00:00
```
auth requisite pam_panic.so auth=< UUID > reject=< UUID > reboot serious=< UUID >
account requisite pam_panic.so
```
2018-03-31 23:53:41 +00:00
### Using the two passwords:
```
auth requisite pam_panic.so password reboot serious=< UUID >
account requisite pam_panic.so
```
2018-03-27 01:32:29 +00:00
See `man 8 pam_panic` for more.
## TODO
2018-03-28 19:46:03 +00:00
- [Manpage translations ](https://github.com/Bandie/pam_panic/issues?q=is%3Aissue+is%3Aopen+label%3Alocalization )
