Skip to content
Browse files

Debug work

  • Loading branch information...
1 parent 5dbde5e commit 7e7296921bcfb6f3b62e5c581d7a3d8f21b76167 @thomasfrivold committed Oct 27, 2013
Showing with 40 additions and 21 deletions.
  1. +7 −1 LUKSUS
  2. +7 −0 LUKSUS.functions
  3. +2 −2 LUKSUS.variables
  4. +24 −18 README
View
8 LUKSUS
@@ -82,7 +82,13 @@ fi
#########################################################
#########################################################
#########################################################
-trap 'EXITHOUSEKEEPING' EXIT # calls housekeeping function on exit. Will be run once for errorlevel 0 and once for every errorlevel 1. awesome.
+set -o noclobber
+set -o errtrace
+set -o errexit
+set -o pipefail
+trap EXITHOUSEKEEPING EXIT # calls housekeeping function on exit. Will be run once for errorlevel 0 and once for every errorlevel 1. awesome.
+trap traperr ERR
+
$DEBUGSTEP
# Calling functions
View
7 LUKSUS.functions
@@ -65,10 +65,17 @@ case $retval in
esac
}
+TRAPERR()
+{
+ echo "ERROR: ${BASH_SOURCE[1]} '' \
+ ''at about line ${BASH_LINENO[0]}"
+}
EXITHOUSEKEEPING()
{
rm *.$$
+rm menuchoices.*
+rm welcomelogo.*
}
View
4 LUKSUS.variables
@@ -1,7 +1,7 @@
# This file contains variables and command substitutions (no more backticks) in variables
programname=LUKSUS
-version=v1.2.35
-date="25.10.2013"
+version=v1.2.40
+date="27.10.2013"
author="Thomas J. Frivold"
time1="$(date +%s.%N)"
# $1, %2, %3, %4 are command line arguments
View
42 README
@@ -26,7 +26,8 @@ Instead of having to read up on the documentation for these
tools, I wrote this wrapper script to handle the dirtywork.
Being opinionated and pragmatic this program assumes that you (must)
have: dialog or whiptail, gnutools / coretools , and a supported
-encryption engine installed.
+encryption engine installed. On Linux this is either found in the
+cryptsetup package for LUKS support and tcplay for Truecrypt support.
# USAGE
@@ -35,6 +36,24 @@ encryption engine installed.
# FAQ:
+Q: What's in the secret sauce?
+This is the gist of the encryption process is this command:
+
+LUKS
+cryptsetup --batch-mode --verbose --key-size=512 --cipher=aes-xts-plain64 luksFormat $device $keyfile
+
+Truecrypt (tcplay)
+tcplay --create --device=$device --cipher=AES-256-XTS
+
+Geli (FreeBSD)
+geli init -s 4096 $device
+
+
+Q: Why are we using the AES-256 cipher?
+A: It is thoroughly vetted and impossible to crack unless Quantum
+Computers become a reality.
+http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html
+
Q: I really want to learn more about crypto in Linux. Where should I start?
A: This Kiwi guy wrote a series of excellent blog posts covering Linux
crypto software and usage of these. I highly recommend reading through them:
@@ -128,23 +147,6 @@ Q: I lost the key or the password, is there a way to restore the key
if I forgot it?
A: No. Really. No.
-Q: What's in the secret sauce?
-This is the gist of the encryption process is this command:
-
-LUKS
-cryptsetup --batch-mode --verbose --key-size=512 --cipher=aes-xts-plain64 luksFormat $device $keyfile
-
-Truecrypt (tcplay)
-tcplay --create --device=$device --cipher=AES-256-XTS
-
-Geli (FreeBSD)
-geli init -s 4096 $device
-
-
-Q: Why are we using the AES-256 cipher?
-A: It is thoroughly vetted and impossible to crack unless Quantum
-Computers become a reality.
-http://www.moserware.com/2009/09/stick-figure-guide-to-advanced.html
Q: ON KEYFILES - ARE THEY BETTER THAN PASSWORDS?
A: Good question, some crypto wizards gave me this answer: -
@@ -455,6 +457,10 @@ v1.3.0
+Extensive testing was done on all platforms
+NetBSD is now properly supported
+v1.2.40 21:30 27.10.2013
+Whiptail options are unstable and troublesome. Support removed until later
+notice, relying on dialog.
+
v1.2.20 00:45 25.10.2013
+The menu system is now complete.
+Code improvements

0 comments on commit 7e72969

Please sign in to comment.
Something went wrong with that request. Please try again.