Adding information about memory poisoning in man page. Fixing #109

src/pam_panic/man/man8/pam_panic.8

@@ -171,6 +171,25 @@ If \fI/dev/disk/by-partuuid\fR is not existent, you can use the ID from \fI/dev/
 You should not issue the panic function if you think that your data has been cloned before. This might cause more problems than it can help you.
 
 
+.SH "ADDITIONAL SECURITY: MEMORY POISONING"
+.PP
+.PD 0
+If you want to be sure to have your memory clear of all information when issuing a reboot/shutdown you might want to add the options 
+.RS 4
+page_poison=on
+.RE
+and
+.RS 4
+slub_debug=P
+.RE
+to your kernel arguments.
+For GRUB2 you just append it on your \fBGRUB_CMDLINE_LINUX\fR entry in \fI/etc/default/grub\fR and generate a new GRUB2 config:
+.RS 4
+grub-mkconfig -o /boot/grub/grub.cfg
+.RE
+.PD 1
+
+
 .SH "RETURN VALUES"
 .PP
 PAM_SUCCESS

src/pam_panic_config/pam_panic_config.prebuild.sh

@@ -82,6 +82,7 @@ NEXT_LOGIN=$(N_ "At your next login you need to")
 TYPEPW=$(N_ "type your pam_panic authentification password or")
 INSRM=$(N_ "insert your removable authentication media")
 PREVTOREG=$(N_ "previous your regular user password.")
+MEMPOISONING=$(N_ "You want more security? Read section ADDITIONAL SECURITY: MEMORY POISONING in the man pages of pam_panic (\"man pam_panic\").")
 QUESTIONS=$(N_ "If you got any question, don't hesitate to ask via IRC (chat.freenode.net in room #pampanic) or via mail + GPG.")
 PRESSENTER=$(N_ "Press enter to exit.")
 
@@ -401,6 +402,7 @@ $NEXT_LOGIN
   - $INSRM
 $PREVTOREG
 
+$MEMPOISONING
 " | more
 
 echo "$QUESTIONS"