The Linux Crypto Undertaker
Go to file
Jaromil a73e0a3519 Merge pull request #28 from davinerd/feat_issue_1
we'll print a warning on 'list' if the tomb is almost full
2011-08-19 06:31:16 -07:00
debian new debian packaging 2011-05-15 19:29:46 +02:00
doc webpage updates for new release 2011-05-29 17:22:26 +02:00
po internationalization 2011-05-09 14:06:30 +02:00
share no terminal 2011-05-26 19:04:46 +02:00
src added check in list_tombs(): if a tomb usage is greater or equals to 90%, then the script prints a warning 2011-08-19 15:25:19 +02:00
.gitignore new debian packaging 2011-05-15 19:29:46 +02:00
.gitmodules fixes in dyne-web submodule 2011-01-26 10:43:49 +01:00
AUTHORS release documentation 2011-04-27 21:38:45 +02:00
ChangeLog documentation for release 2011-05-26 19:21:09 +02:00
configure.ac fixing mime defaults and icon installations 2011-05-26 16:43:54 +02:00
COPYING New repository for Tomb 2010-08-22 15:04:19 +02:00
HACKING Simple style guidelines, as discussed in ML 2011-05-02 11:15:11 +02:00
INSTALL New repository for Tomb 2010-08-22 15:04:19 +02:00
Makefile.am deactivate intl and po builds for now 2011-05-10 10:38:18 +02:00
NEWS New repository for Tomb 2010-08-22 15:04:19 +02:00
README documentation for release 2011-05-26 19:21:09 +02:00
TODO.org documentation for release 2011-05-26 19:21:09 +02:00

    .....                                                ..
 .H8888888h.  ~-.                                  . uW8"
 888888888888x  `>        u.      ..    .     :    `t888
X~     `?888888hx~  ...ue888b   .888: x888  x888.   8888   .
'      x8.^"*88*"   888R Y888r ~`8888~'888X`?888f`  9888.z88N
 `-:- X8888x        888R I888>   X888  888X '888>   9888  888E
      488888>       888R I888>   X888  888X '888>   9888  888E
    .. `"88*        888R I888>   X888  888X '888>   9888  888E
  x88888nX"      . u8888cJ888    X888  888X '888>   9888  888E
 !"*8888888n..  :   "*888*P"    "*88%""*88" '888!` .8888  888"
'    "*88888888*      'Y"         `~    "    `"`    `%888*%"
        ^"***"`                                        "`

a simple commandline tool to manage encrypted storage  v.1.1

                   http://tomb.dyne.org


Tomb aims to be a free and open source system for easy encryption and
backup of personal files, written in code that is easy to review and
links shared OS components.

At present time, Tomb consists of a simple shell script (Zsh) using
standard filesystem tools (GNU) and the cryptographic API of the Linux
kernel (cryptsetup and LUKS), plus a status tray application which
integrates in your desktop.

** Who needs Tomb

Our target community are desktop users with no time to click around,
sometimes using old or borrowed computers, operating in places
endangered by conflict where a leak of personal data can be a threat.

If you don't own a laptop then it's possible to go around with a USB
stick and borrow computers, still leaving no trace and keeping your
data safe during transports. Tomb aims to facilitate all this and to
be interoperable across popular GNU/Linux operating systems.

** How does it works

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.

** Stage of development

Tomb is an evolution of the 'mknest' tool developed for the dyne:bolic
GNU/Linux distribution, which is used by its 'nesting' mechanism to
encrypt the Home directory of users.

As such, it uses well tested and reviewed routines and its shell code
is pretty readable. The name transition from 'mknest' to 'tomb' is
marked by the adaptation of mknest to work on the Debian operating
system, used by its author in the past 3 years.

** How can you help

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.

Enthusiastic ideas are in the TODO file.

Donations are always welcome, see http://dyne.org/donate

More about who is currently involved in the AUTHORS file.