trelease documentation updates - tomb - the crypto undertaker
HTML git clone git://parazyd.org/tomb.git
DIR Log
DIR Files
DIR Refs
DIR README
DIR LICENSE
---
DIR commit 58f7248378455285ab28c8907c9325d9415d9bfc
DIR parent 10baee25a6217d7b6cd80f28e0533d7d615f346e
HTML Author: Jaromil <jaromil@dyne.org>
Date: Mon, 13 Jan 2014 13:54:16 +0100
release documentation updates
Diffstat:
M ChangeLog | 8 ++++++++
M KNOWN_BUGS | 5 +++--
M README | 6 +++---
3 files changed, 14 insertions(+), 5 deletions(-)
---
DIR diff --git a/ChangeLog b/ChangeLog
t@@ -1,3 +1,11 @@
+January 2014 - 1.5
+ Minor bugfixes to documentation, error handling, support for
+ multiple and encrypted swap partitions and qr code engraving.
+ This release also includes some minor code refactoring of
+ load_key() and loop mount checks. Also the tray app is updated
+ to gtk-3 and works simply with a tomb name as argument.
+ Documentation was updated accordingly.
+
June 2013 - 1.4
This release fixes an important bug affecting Tomb 1.3.* which
DIR diff --git a/KNOWN_BUGS b/KNOWN_BUGS
t@@ -1,4 +1,4 @@
-* Compatibility broken in Tomb 1.3 and 1.3.1
+* Compatibility broken in old Tomb 1.3 and 1.3.1
Due to an error in the creation and decoding of key files, release
versions 1.3 and 1.3.1 cannot open older tombs, plus the tombs created
t@@ -16,4 +16,5 @@
This bug was due to a typo in the code which appended a GnuPG status
string to the content of keys. All users of Tomb 1.3.* should pay
- particular attention to this issue.
+ particular attention to this issue, however that release series was
+ out as latest for less than a month.
DIR diff --git a/README b/README
t@@ -12,9 +12,9 @@ X~ `?888888hx~ ...ue888b .888: x888 x888. 8888 .
' "*88888888* 'Y" `~ " `"` `%888*%"
^"***"` "`
-A minimalistic commandline tool to manage encrypted volumes v.1.4
+A minimalistic commandline tool to manage encrypted volumes v1.5
- http://tomb.dyne.org
+ http://dyne.org/software/tomb
Tomb aims to be a free and open source system for easy encryption and
t@@ -79,7 +79,7 @@ CBC-ESSIV encryption algorithm.
** How can you help
-Donations are always welcome, see http://dyne.org/donate
+Donations are always welcome, see https://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