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

Merge pull request #17 from jordydickinson/master 

Stylistic revisions of README.md
This commit is contained in:
Bandie 2018-03-28 22:07:20 +02:00 committed by GitHub
parent 378e58c232 29eca690bf
commit 7888100abb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@ -2,29 +2,25 @@
## Purpose ## Purpose
The pam\_panic PAM module shall protect people who have value data on their computer. It provides a panic function. pam\_panic is a PAM module that protects sensitive data and provices a panic function for emergency situations.
## How it works ## How it works
There are two removable media which work as keys: One is the auth key and one is the panic key. 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.
The auth key will let you pass to the password prompt.
The panic key will execute a reboot, poweroff and/or erase the luksHeader which will make your luksContainer undecryptable to anyone.
## Installation ## Installation
You need gcc or something similar. 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 you may want to do the following within this project directory:
To compile and install it, do the following within the project's root directory:
``` ```
make make
sudo make install sudo make install
``` ```
### Compiling notes Note: the paths of the `reboot`, `poweroff`, and `cryptsetup` commands are passed to the module at compile-time.
The Makefile passes the pathes of `reboot`, `poweroff` and `cryptsetup` using macros to be sure that it will run on different machines.
You need libpam's development package. Some call them `libpam0g-dev`.
## Preparation ## Preparation
You need two GPT formatted removable devices. There must be at least one partition on it. Here is an example with `fdisk`: 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:
``` ```
$ sudo fdisk /dev/sdc $ sudo fdisk /dev/sdc
@ -48,9 +44,8 @@ Command (m for help): w
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. 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.
## Configuration
## Integration To configure the module, add the following to the appropriate PAM configuration file(s): (see pam.conf(5) for details on these files)
To let it integrate with your system, add the following at the top of of your pam.d config(s):
``` ```
@ -62,5 +57,5 @@ See `man 8 pam_panic` for more.
## TODO ## TODO
- Asking for [man page translations](https://github.com/Bandie/pam_panic/issues?q=is%3Aissue+is%3Aopen+label%3Alocalization) - [Manpage translations](https://github.com/Bandie/pam_panic/issues?q=is%3Aissue+is%3Aopen+label%3Alocalization)
- Integrate [panic password](https://github.com/Bandie/pam_panic/issues/7) - Integrate [panic password](https://github.com/Bandie/pam_panic/issues/7)