Tomb-open is a lightweight wrapper and currently has no way to warn the user about
a swap being present. for now we simply deactivate the check.
In future, tombs will be created with a new GUI and this wrapper will be left
only for xdg registered operations (file manager right click, mime-types etc.)
This commit fixes issue #62
It was putting the option BEFORE the subcommand.
However, the new method supports this only partially:
* Boolean options can be put before the subcommand
* Subcommand-specific options that take an argument can be put before the
subcommand, only in the
form -kvalue ; using -k value gives an error
* Global options can always be put before the subcommand
Therefore, we'll say that options MUST go after the subcommand (to stay sure)
and notice if tomb hasn't right permissions
in future we should check permissions of tomb from the suid commandline
this way we can also change its permissions and make it ours
it would be ideal to make tomb-open never use 'sudo' but create
internal tasks in tomb (like mktemp), this way if we enable users to
create tombs on a system then just the full path to binary tomb is
necessary in sudoers....
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
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
