commit bbb290c81a30fdf5f285a0b8d01a6c2338206791
parent a0db66b18e4b9aa994d079762f9d4d1bacdd7eee
Author: Jaromil <jaromil@dyne.org>
Date: Sun, 16 Nov 2014 13:55:51 +0100
documentation updates
Diffstat:
4 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/ChangeLog.md b/ChangeLog.md
@@ -4,14 +4,17 @@
### November 2014
Tomb goes international: now translated to Russian, French, Spanish
-and German. GNU gettext required.
-The usability of steganography has improved: images can now be used
+and German.
+
+The usability has improved: steganographed images can now be used
directly as keys (-k). Piping keys to stdin now works also across ssh
-connections. Security improved by avoiding most uses of temporary files.
-All code has been refactored for readability and integration with zsh
-features. Signal handlers are now in place, global arrays are used to
-keep track of temp files. Namespace has been revisioned and corrected,
-described in [HACKING](docs/HACKING.txt).
+connections.
+
+The security is also improved by avoiding most uses of temporary
+files. All code has been refactored for readability and integration
+with zsh features. Signal handlers are now in place, global arrays are
+used to keep track of temp files. Namespace has been revisioned and
+corrected, described in [HACKING](docs/HACKING.txt).
## 1.5.3
### June 2014
diff --git a/KNOWN_BUGS.md b/KNOWN_BUGS.md
@@ -21,8 +21,9 @@
and be able to operate their tombs normally.
Those who have used Tomb 1.3 or 1.3.1 to create new tombs should use
- Tomb version 1.3.1 to open them and then migrate the contents into a
- new tomb created using the latest Tomb version.
+ Tomb version 1.3.1 (available from https://files.dyne.org/tomb) to
+ open them and then migrate the contents into a new tomb created using
+ the latest stable Tomb version.
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
diff --git a/README.md b/README.md
@@ -14,9 +14,9 @@
*A minimalistic commandline tool to manage encrypted volumes* aka **The Crypto Undertaker**
-Latest stable version: **1.5.3**
+Latest stable version: **2.0**
-Updates on website: http://dyne.org/software/tomb
+Updates on website: https://www.dyne.org/software/tomb
Get the stable .tar.gz signed release for production use!
Download it from https://files.dyne.org/tomb
@@ -94,8 +94,8 @@ always ensure backward compatibility with older tombs: we make sure it
creates sane tombs and keys by running various tests before releasing
it. The development version in Git might introduce sudden bugs and is
not guaranteed to produce backward- or forward-compatible tombs and keys.
-Only developers and testers should use the Git version to report bugs,
-test new features, and develop patches.
+The development version in Git should be used to report bugs, test new
+features and develop patches.
So be warned: do not use the latest Git version in production
environments, but use a stable release versioned and packed as
diff --git a/tomb b/tomb
@@ -2655,13 +2655,13 @@ _print "Tomb ::1 version:: - a strong and gentle undertaker for your secrets" $V
_print "\000"
_print " Copyright (C) 2007-2014 Dyne.org Foundation, License GNU GPL v3+"
_print " This is free software: you are free to change and redistribute it"
-_print " The latest Tomb sourcecode is published on <http://tomb.dyne.org>"
+_print " For the latest sourcecode go to <http://dyne.org/software/tomb>"
_print "\000"
option_is_set -v && {
_print " This source code is distributed in the hope that it will be useful,"
_print " but WITHOUT ANY WARRANTY; without even the implied warranty of"
_print " MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE."
-_print " Please refer to the GNU Public License for more details."
+_print " When in need please refer to <http://dyne.org/support>."
_print "\000"
_print "System utils:"
_print "\000"
