TODO and Roadmap for Tomb
you are welcome to send patches to [email protected]
Issue tracking is now handled via GitHub, see http://github.com/dyne/Tomb
Old roadmap notes:
Must be 100% backward compatible with tombs created with 1.0
Started generating the strings, still need to figure out how to install it
a graphical tool or text wizard to move keys in/out steganography as well split them
inotify can also count when was the last time tomb was used and unmount it automatically after a timeout, see how much free space is left and warn when the space is almost finished
gksu is deeply connected to gnome in all its packages. actually libgksu2-dev is and that doesn’t helps.
gksu binary is a very simple and dirty code, we should have tomb-ask to use the libgksu library for privilege escalation, but then this would add the dependency into C linking…
the solution is for now to detect if gksu is present, else fallback to sudo and provide it an interface to ask the password graphically via pinentry
using lsof and fuser(1) we can do that easily
we should ask user confirmation when closing a tomb if to slam
tomb-askpass will become tomb-ask managing such user interaction, using libassuan and pinentry from the gpg project.
steghide can hide keys in JPG, BMP, WAV or AU files it also takes care of compressing end encrypting the key file so we don’t necessarily need gpg… it has Serpent and AES256 (CBC)
done as file ‘bind-hooks’ inside tom. also ‘post-hooks’ is executed as user in case symlinks are needed and so
using mount -o bind we can trigger actions to be made after mounting a tomb so that personal directories appear in the home folder.
using FReeOTFE http://www.freeotfe.org
or at least make it compatible with http://www.sdean12.org/SecureTrayUtil.htm
still to be investigated what’s there that supports cryptsetup-luks volumes