Anathema
1b4c08e904
fix #55 : deleted obsolete $NOBIND global var and used the more powerful option_is_set() function to check wheatever the -n flag is missing or not
2011-10-26 12:02:46 +02:00
Jaromil
72fcc7c2f5
Merge branch 'fix_user_home_search'
2011-10-26 11:58:19 +02:00
Anathema
e7e71aa002
fix #52 : when trying to get user home directory in exec_safe_bind_hooks, the grep and sed commands doesn't output the right result when multiple lines occours.
...
Now, we use awk to do so
2011-10-26 11:58:05 +02:00
Jaromil
5d54a3b121
Merge pull request #53 from davinerd/fix_remove_mountpoint_51
...
Removing default mount point when umounting the tomb
2011-10-25 15:14:29 -07:00
Anathema
350eeb7483
fix #51 : added a check into umount_tomb() before removing mount point: if it's the default one, then delete it
2011-10-25 19:37:28 +02:00
Jaromil
262855fa10
Merge pull request #50 from boyska/exitcode
...
Better exit code handling, #49
2011-10-24 13:12:08 -07:00
BoySka
69eca5c1d7
Better exit code handling, #49
2011-10-24 21:43:58 +02:00
boyska
3c09c5d81f
man doc: minor fixes
2011-09-26 11:49:28 +02:00
boyska
9de97225c4
MAN doc: -k -
2011-09-26 11:49:28 +02:00
boyska
f4b8a2275e
Update documentation: swap, --ignore-swap, -k
2011-09-26 11:49:28 +02:00
Jaromil
a3f0c7c86b
clean up mount code and list output ( fix #32 )
2011-09-26 11:33:07 +02:00
Anathema
70e4a5d19f
fixed #40 , added a check to $keyfile in decode_key(), which abort the execution of tomb in case of keyfile already present
2011-09-26 10:55:22 +02:00
Jaromil
86db18b386
Merge pull request #48 from boyska/fix_47_gpgpwd
...
FIX #47 : handling of special chars in password
2011-09-25 04:05:01 -07:00
boyska
4fa04ee94b
FIX #47 : handling of special chars in password
2011-09-17 01:30:15 +02:00
Jaromil
a752005271
tomb-status launcher in a command 'status'
2011-09-04 09:36:40 +02:00
Jaromil
ec43b959df
fixes for desktop integration
2011-09-03 14:09:25 +02:00
Jaromil
cb6fa07416
fixed tomb umount
...
correctly checks error status of umount
2011-09-03 12:43:21 +02:00
Jaromil
5eebc89e48
fix correct use of mktemp
2011-09-03 12:39:17 +02:00
boyska
f0cd7f50a2
FIX #36 pinentry and password with spaces
2011-08-30 00:40:04 +02:00
(A)nathema
ab7beebfc9
Merge pull request #41 from davinerd/feat_set_keyname
...
added key file extension when a key name is specified
2011-08-29 14:56:07 -07:00
Anathema
d486c45f53
added extension .tomb.key to a specified key file (-k param)
2011-08-29 23:52:50 +02:00
nignux
d979ebc332
Merge pull request #35 from davinerd/fix_permissions_tomb
...
fixed chown and chmod tomb file
2011-08-29 05:09:03 -07:00
Anathema
9fbb620c60
added feature #25 : an user can now specify a key name when creating tomb, using the -k flag
2011-08-28 20:21:10 +02:00
boyska
ce7edc1b63
FTR #31 : support key from stdin with -k -
...
This will be useful for integration with external tools/undertaker
2011-08-28 19:28:47 +02:00
boyska
13a9142949
FIX option_value problems with "strange" values
2011-08-28 19:28:30 +02:00
Anathema
f2ba4136b8
Fixed integer checking of -s param
2011-08-28 17:24:55 +02:00
Jaromil
3fe53affc9
webpage updates
...
added links to github, crypto.is and our cheerful picture after the hackmeeting tomb seminar
2011-08-25 09:37:28 +02:00
Anathema
fdcdd52407
fixed chown and chmod tomb file path, that prevents from change the owner and permissions on newly created tomb
2011-08-23 16:55:46 +02:00
boyska
103788f2da
FIX mime packaging problems
2011-08-21 18:52:10 +02:00
boyska
f8e9837dc1
FIX help was "always" showing up
...
Actually, showing up IFF sudo has a cached password
2011-08-20 19:25:11 +02:00
Jaromil
3d611d2fb4
new opt parse missed 'source' command, now in place
2011-08-20 18:45:00 +02:00
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
Anathema
7b08b49e97
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
boyska
938cb01af0
Use rmdir instead of rm -r (refs #7 )
...
rm -r is too dangerous.
use 'rmdir' instead: it aborts if dir is not empty.
As suggested by jamiromimil:
https://github.com/dyne/Tomb/issues/7#issuecomment-1724892
2011-08-18 19:14:46 +02:00
boyska
1eb5157b9a
Fix #7 tomb's mountpoint persistence
2011-08-18 19:14:46 +02:00
boyska
9c9e33500e
More readable option check
2011-08-18 19:14:42 +02:00
boyska
7e4a56d9c6
check if swap is on; fixes #4
...
Tomb will abort with errors if swap is on (for open and create subcommands);
however, you can force it using --ignore-swap.
2011-08-18 19:14:42 +02:00
(A)nathema
f76a355fd0
Merge pull request #24 from davinerd/feat_issue_21
...
Feat issue 21
2011-08-18 09:49:38 -07:00
BoySka
4d4d69cd4d
Merge pull request #22 from boyska/fix_nosubcmd
...
tomb -h and tomb -v work as expected, without altering any other command
(it uses a __default subcommand if none is given)
2011-08-18 04:30:40 -07:00
Anathema
7584dc72e7
added support for the --force option, which cause slam_tomb() to not wait 3 secs between kills
2011-08-18 11:01:17 +02:00
Anathema
a5807344d5
fix invalid kill with multiple pids
2011-08-18 00:16:00 +02:00
boyska
582cce9f66
./tomb -v works fine
...
Fixed the "--verbose" alias: it should have been --version
2011-08-16 20:51:59 +02:00
boyska
32ee4c7c5d
If no subcmd use a default. tomb -h or -v works
2011-08-16 20:44:18 +02:00
Anathema
20c1097281
feature request #21 , now slam_tomb() tries to kill 3 times the pids holding the tomb, workflow:
...
1- kill -SIGUSR1
2- if there are remaining pids, wait 3 secs to get harder
3- kill -SIGTERM
4- if there are remaining pids, wait 3 secs to kill 'em all
5- kill -SIGKILL
2011-08-16 02:52:01 +02:00
Anathema
afd785be62
fixed issue #20 : created slam_tomb() that take cares about killing and checking pids
2011-08-16 02:43:15 +02:00
Jaromil
21be9e204e
Merge pull request #18 from boyska/only_optparsing
...
New CLI option parsing supports contextual options following commands.
ZSH functions are used to parse options. Further testing will follow.
2011-08-03 23:58:14 -07:00
boyska
a252f62fba
Fix #14 : problems with spaces in option arguments
2011-08-02 02:55:00 +02:00
boyska
d5ca1885ca
[Optparsing] do a shift to delete subcommand
2011-08-02 02:55:00 +02:00
boyska
6495099344
[Optparsing] Support options in whatever position
...
However, it has a precondition that developers MUST respect:
An option CAN'T have differente meanings/behaviour in different subcommands.
For example, "-s" means "size" and accept an argument. If you are tempted to add
an option "-s" (that means, for example "silent", and doesn't accept an argument)
This, however, make sense even from an usability point of view.
Also, option with optional argument are prohibited.
The technique is a "double scan": first, we scan options passing
_every_ possible subcommand options to zparseopts.
This way, we can distinguish between option argument and parameters.
So, we recognize which is the subcommand.
Then, parse again
2011-08-02 02:55:00 +02:00
boyska
d0e004412d
Changing optparsing, tomb-open needs changes
...
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)
2011-08-02 02:55:00 +02:00
