refinements to the website

This commit is contained in:
Jaromil 2011-01-26 16:01:53 +01:00
parent 2b9a24802b
commit 5a9f754eae

View File

@ -3,7 +3,11 @@
<contents> <contents>
* Tomb - RIP * Tomb - Crypto Undertaker
<class name="logo">
[[images/tomb_n_bats.png]]
</class>
<example> <example>
@ -21,7 +25,7 @@ X~ `?888888hx~ ...ue888b .888: x888 x888. 8888 .
^"***"` "` ^"***"` "`
a simple commandline tool to manage encrypted storage v.0.9 a simple commandline tool to manage encrypted storage v.0.9
http://tomb.dyne.org by Jaromil @ dyne.org by Jaromil @ dyne.org
</example> </example>
** Introduction ** Introduction
@ -51,34 +55,41 @@ We've felt the urgency of publishing Tomb for other operating systems
than dyne:bolic since the current situation with [[http://en.wikipedia.org/wiki/TrueCrypt][TrueCrypt]] is far from than dyne:bolic since the current situation with [[http://en.wikipedia.org/wiki/TrueCrypt][TrueCrypt]] is far from
optimal. TrueCrypt makes use of statically linked libraries, its code optimal. TrueCrypt makes use of statically linked libraries, its code
is not hosted on CVS and is [[http://lists.freedesktop.org/archives/distributions/2008-October/000276.html][not considered free]] by GNU/Linux is not hosted on CVS and is [[http://lists.freedesktop.org/archives/distributions/2008-October/000276.html][not considered free]] by GNU/Linux
distributions because of liability reasons, see [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364034][Debian]], [[https://bugs.edge.launchpad.net/ubuntu/+bug/109701][Ubuntu]][4], distributions because of liability reasons, see [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364034][Debian]], [[https://bugs.edge.launchpad.net/ubuntu/+bug/109701][Ubuntu]],
Suse[5], Gentoo[6] and Fedora[7]. [[http://lists.opensuse.org/opensuse-buildservice/2008-10/msg00055.html][Suse]], [[http://bugs.gentoo.org/show_bug.cgi?id=241650][Gentoo]] and [[https://fedoraproject.org/wiki/ForbiddenItems#TrueCrypt][Fedora]].
Seen from this perspective, Tomb is intended as a rewrite of most Seen from this perspective, Tomb is intended as a rewrite of most
functionalities offered by TrueCrypt in a new application, confident functionality offered by TrueCrypt in a new application, confident it
it won't take much relying on previous experience and aiming at: won't take much relying on previous experience and aiming at:
- short and readable code, linking shared libs and common components - short and readable code, linking shared libs and common components
- easy graphical interface, simple for ad-hoc (DIY-deniable) - easy graphical interface, simple for ad-hoc (DIY-deniable)
- transparent and distributed development hosted using GIT - transparent and distributed development hosted using GIT
- GNU General Public License v3 - GNU General Public License v3
[1] http://en.wikipedia.org/wiki/TrueCrypt
[2] http://lists.freedesktop.org/archives/distributions/2008-October/000276.html
[3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=364034
[4] https://bugs.edge.launchpad.net/ubuntu/+bug/109701
[5] http://lists.opensuse.org/opensuse-buildservice/2008-10/msg00055.html
[6] http://bugs.gentoo.org/show\_bug.cgi?id=241650
[7] https://fedoraproject.org/wiki/ForbiddenItems#TrueCrypt
*** How does it works *** How does it works
Tombs are operated from a normal file browser or from the commandline.
To open a tomb is sufficient to click on it, or use the command **tomb-open**
[[images/monmort.png]]
When a tomb is open your panel will have a little icon in the tray
reminding you that a tomb is open, offering to explore it or close it.
Tomb generates 'key files' and protects them with a password choosen Tomb generates 'key files' and protects them with a password choosen
by the user; the key files are then used to encrypt loop-back mounted by the user; the key files are then used to encrypt loop-back mounted
partitions, like single files containing a filesystem inside: this way partitions, like single files containing a filesystem inside: this way
keys can be separated from data for safer transports when keys can be separated from data for safer transports when
required. required.
For more information on how to operate Tomb from the commandline, the
backend tool **tomb** comes complete with a brief --help and a
[[manual][manual page]].
** Downloads ** Downloads
For licensing information see the [[http://www.gnu.org/copyleft/gpl.html][GNU General Public License]] For licensing information see the [[http://www.gnu.org/copyleft/gpl.html][GNU General Public License]]