mirror of
https://github.com/Llewellynvdm/Tomb.git
synced 2025-01-09 08:29:50 +00:00
refinements to the website
This commit is contained in:
parent
2b9a24802b
commit
5a9f754eae
@ -3,7 +3,11 @@
|
||||
|
||||
<contents>
|
||||
|
||||
* Tomb - RIP
|
||||
* Tomb - Crypto Undertaker
|
||||
|
||||
<class name="logo">
|
||||
[[images/tomb_n_bats.png]]
|
||||
</class>
|
||||
|
||||
|
||||
<example>
|
||||
@ -21,7 +25,7 @@ X~ `?888888hx~ ...ue888b .888: x888 x888. 8888 .
|
||||
^"***"` "`
|
||||
|
||||
a simple commandline tool to manage encrypted storage v.0.9
|
||||
http://tomb.dyne.org by Jaromil @ dyne.org
|
||||
by Jaromil @ dyne.org
|
||||
</example>
|
||||
|
||||
** 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
|
||||
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
|
||||
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],
|
||||
Suse[5], Gentoo[6] and Fedora[7].
|
||||
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]],
|
||||
[[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
|
||||
functionalities offered by TrueCrypt in a new application, confident
|
||||
it won't take much relying on previous experience and aiming at:
|
||||
functionality offered by TrueCrypt in a new application, confident it
|
||||
won't take much relying on previous experience and aiming at:
|
||||
|
||||
- short and readable code, linking shared libs and common components
|
||||
- easy graphical interface, simple for ad-hoc (DIY-deniable)
|
||||
- transparent and distributed development hosted using GIT
|
||||
- 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
|
||||
|
||||
|
||||
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
|
||||
by the user; the key files are then used to encrypt loop-back mounted
|
||||
partitions, like single files containing a filesystem inside: this way
|
||||
keys can be separated from data for safer transports when
|
||||
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
|
||||
|
||||
For licensing information see the [[http://www.gnu.org/copyleft/gpl.html][GNU General Public License]]
|
||||
|
Loading…
Reference in New Issue
Block a user