commit ed879974cd535677aa5c60e0fbba6d40894d0994
parent c16402b04b8c745621061ee27401074e8fbdf216
Author: Jaromil <jaromil@dyne.org>
Date: Wed, 12 Jun 2013 14:28:40 +0200
documentation updates for release
Diffstat:
5 files changed, 39 insertions(+), 15 deletions(-)
diff --git a/AUTHORS b/AUTHORS
@@ -10,5 +10,8 @@ Asbesto Molesto and Nignux.
Cryptsetup was developed by Christophe Saout and Clemens Fruhwirth
+Tomb includes an implementation of the "Password-Based Key Derivation
+Function v2" based on GCrypt and written by by Anthony Thyssen
+
Tomb's developers can be contacted via the "crypto" mailinglist on
-http://lists.dyne.org
+http://lists.dyne.org or on IRC https://irc.dyne.org channel #dyne
diff --git a/ChangeLog b/ChangeLog
@@ -1,3 +1,13 @@
+June 2013 - 1.3.1
+
+ Major bugfixes following the recent refactoring. This release
+ fixes various advanced commands as search/index, KDF key
+ protection against dictionary attacks and steganographic hiding of
+ keys. It provides compatibility across GnuPG 1.4.11 and .12 which
+ broke the decoding of keys. Usage of commandline option is made
+ consistent and full paths are honored. A new test suite is
+ included and documentation is updated accordingly.
+
May 2013 - 1.3
A refactoring of Tomb's main script internals was made, including
diff --git a/README b/README
@@ -12,7 +12,7 @@ X~ `?888888hx~ ...ue888b .888: x888 x888. 8888 .
' "*88888888* 'Y" `~ " `"` `%888*%"
^"***"` "`
-A minimalistic commandline tool to manage encrypted volumes v.1.3
+A minimalistic commandline tool to manage encrypted volumes v.1.3.1
http://tomb.dyne.org
@@ -79,15 +79,17 @@ CBC-ESSIV encryption algorithm.
** How can you help
+Donations are always welcome, see http://dyne.org/donate
+
Code is pretty short and readable: start looking around it and the
materials found in doc/ which are good pointers at security measures
to be further implemented.
-Tomb's developers can be contacted via the "crypto" mailinglist on
-http://lists.dyne.org
+For the bleeding edge visit https://github.com/dyne/Tomb
-Enthusiastic ideas are in the TODO file.
+Tomb's developers can be contacted via the "crypto" mailinglist on
+http://lists.dyne.org or via IRC on https://irc.dyne.org channel #dyne
-Donations are always welcome, see http://dyne.org/donate
+Some enthusiastic ideas are in the TODO file.
Information on developers involved is found in the AUTHORS file.
diff --git a/doc/tomb.1 b/doc/tomb.1
@@ -261,8 +261,11 @@ Create a 128MB large "secret" tomb and its keys, then open it:
.EX
tomb dig -s 128 secret.tomb
+
tomb forge secret.tomb.key
+
tomb lock secret.tomb -k secret.tomb.key
+
tomb open secret.tomb -k secret.tomb.key
.EE
@@ -280,10 +283,13 @@ makes it reachable from the standard $HOME/.gnupg location every time
the tomb will be opened:
.EX
- tomb open GPG.tomb
+ tomb open GPG.tomb -k GPG.tomb.key
+
echo ".gnupg .gnupg" > /media/GPG.tomb/bind-hooks
+
mv ~/.gnupg /media/GPG.tomb/.gnupg && mkdir ~/.gnupg
- tomb close GPG && tomb open GPG.tomb
+
+ tomb close GPG && tomb open GPG.tomb -k GPG.tomb.key
.EE
.IP \(bu
@@ -291,14 +297,22 @@ Create an exec post hook that launches a Firefox browser every time
the tomb will be opened, keeping all its profile data inside it:
.EX
- tomb open FOX.tomb
+ tomb open FOX.tomb -k FOX.tomb.key
+
touch /media/FOX.tomb/post-hooks
+
chmod +x /media/FOX.tomb/post-hooks
+
cat <<EOF >> /media/FOX.tomb/post-hooks
+
#!/usr/bin/env bash
+
if [ "$1" == open ]; then
+
firefox -no-remote -profile $(dirname $0)/firefox_prof &
+
fi
+
EOF
.EE
@@ -307,12 +321,7 @@ Please report bugs on the tracker at
.UR https://bugs.dyne.org
.UE
-Get in touch with developers via mail by subscribing the "crypto" mailinglist
-.UR http://lists.dyne.org
-.UE
-or via the #dyne chat channel on
-.UR https://irc.dyne.org
-.UE
+Get in touch with developers via mail by subscribing the "crypto" mailinglist on \fIhttp://lists.dyne.org\fR or via the #dyne chat channel on \fIhttps://irc.dyne.org\fR.
.SH AUTHORS
diff --git a/doc/tomb_manpage.pdf b/doc/tomb_manpage.pdf
Binary files differ.
