Create is quite good, but has no support for automatic-key-on-usb
Open is very raw, it only supports opening while explicitly choosing
where to get the key from
Python wrapper for tomb is in a distinct library, called "tomblib":
it currently supports tomb, basic undertaker, and parsing output
messages
pytomb: adds undertaker, better parser (updated for new tomb messages)
undertaker: fix some things to make it work with new tomb
the rest is ui stuff :)
the ui does:
- allow auto-searching for the key near the tomb itself
- allow manually choosing a key location
- mount the tomb ;)
the ui DOESN'T:
- support usb nor anything else (shouldn't be that difficult)
- support periodical polling
- anything else
Now pytomb/ contains the python library, which will be available as tomblib
qt/ contains only the qt gui
They all are directly under src/
Also, tomblib has a setup.py to install/package/develop
Warning: sudo behave strangely when watching both stdout and stderr
It seems to be solved watching only stderr, which is where 99% of tomb
output goes, but this is quite an hack
they were deprecated. If you really need, use $PARAM array instead.
But you probably DON'T need to; it's better to make your function directly
accept parameters (btw, mandatory options should probably be parameters, too)
merging boyska's branch to current master
changes some previous names of options:
--path --batch --poll
work in progress, refers to issues: #71#70#69#58#42#27#5
which just rewrites to /path/to/grave.tomb.key
Stupid, but nice to have. Also, could be good if changing the way
we create the key (a move from gpg to pbkdf2 is planned)
Now checks for GnuPG and lists available ciphers
Some more information about the tomb opened is retrieved via cryptsetup
Also some duplicate strings were eliminated and year notices were updated
The new 'resize' command lets a user increase the size of the tomb
The operation is quite lengthy as it requires the creation of a new
tomb file and then copying all contents from the old tomb to the new.
