we require users to have the mount targets for hooks already existing
this behaviour is less intrusive in someone's home that is unconscious of hooks
plus it now supports mount bind of normal files
rename your keys !
this change was motivated by the fact gpg tends to overwrite the
.tomb file if we decrypt the tomb.gpg by hand. changing the extension
in .tomb.key this doesn't happens.
tomb shell command doesn't depends from X,
all GUI notifications are moved into tomb-open including USB key handling,
gksu has been dropped completely as a method to gain privileges,
there is a new -n flag to avoid processing hooks,
variable names have been sanitized, duplicate code eliminated,
documentation has been updated and the code cleaned up
we are very close to the 1.0 now
using pinentry (with Assuan protocol) instead of our own askpass
a bit less cooler but much more secure.
this also includes partial normalization of variable names
and the redirection of tomb operational output to stderr.
Now, the post-hooks is passed an argument (open or close) that can be
used to launch commands when the tomb opens or closes, respectively.
This patch also introduces a safer version of bind-hooks that doesn,t
eval the contents, but read a map:
local/to/tomb local/to/HOME
The local/to/HOME is hardly enforced ATM.
just from the tomb commandline for now (we start missing a simple GUI wizard eh)
also includes fixes for backward compat (renames tomb volumes after files)
this helps scripts track all mounted tombs via mount -l which prints labels
and some tomb-open wrapper fixes too
