summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* minor typo in authorsHEADmasterJaromil10 days1-3/+0
|
* version bumpv2.4Jaromil10 days2-4/+4
|
* updated README with recent help screenJaromil11 days1-10/+11
|
* documentation updatesJaromil11 days4-12/+56
|
* manual updated with actual gpg id usage informationJaromil11 days1-35/+29
|
* minor corrections to new gpg related message formattingJaromil11 days1-2/+2
|
* add debug message of loop device in umount_tombJaromil11 days1-0/+1
|
* Merge pull request #256 from roddhjav/gpg-optionsJaromil11 days3-41/+34
|\ | | | | Options for GnuPG Key - 2
| * Support for gpg encrypted tomb key loaded from stdin. See #255refs/pull/256/headAlexandre Pujol2017-04-051-6/+1
| |
| * Fix issues with GPG default key.Alexandre Pujol2017-04-033-7/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | - Remove --no-options gpg option when using GPG key. - Improve gpg default key tests To use the default key, ~/.gnupg/gpg.conf needs: default-key <keyid> default-recipient-self Or default-recipient <keyid> Otherwise the first key in the keyring is used.
| * Remove --shared flag when sharing a tomb key. See #252Alexandre Pujol2017-03-242-28/+16
|/
* make documentation less opinionated about the u/random issueJaromil2017-03-221-17/+21
| | | | fix #253
* Merge pull request #250 from roddhjav/gpg-supportJaromil2017-03-202-38/+87
|\ | | | | Options for GnuPG Key
| * Fix compatibility with GnuPG 2.2.19refs/pull/250/headAlexandre Pujol2017-03-201-2/+2
| | | | | | | | | | GnuPG 2.2.19 added a warning when no command was given. Some invocations do not specify a command, added --decrypt in this these cases.
| * Fix issue #251Alexandre Pujol2017-03-201-5/+5
| |
| * Add support for non hidden and hidden recipientAlexandre Pujol2017-03-032-18/+45
| | | | | | | | | | Use -r to provide non-hidden recipient, Use -R to provide hidden recipient.
| * Add GPG default key support for key encryptionAlexandre Pujol2017-03-032-22/+44
| | | | | | | | | | If the option -r is not set, use the gpg default key to encrypt a tomb key
* | information about compatible softwareJaromil2017-03-181-0/+19
|/
* updated manual to reflect final stage of gpg asymmetric encryptionJaromil2017-02-211-43/+50
|
* small improvement to ISO compliancy documentationJaromil2017-02-201-6/+11
|
* failed bind-hooks (missing target) no more abort the mount operationJaromil2017-02-201-2/+2
| | | | a warning is printed and the mounting goes forward without the hooks
* Merge pull request #244 from roddhjav/gnupg-key-supportJaromil2017-02-207-106/+452
|\ | | | | GnuPG Key Support
| * Merge branch 'master' into gnupg-key-supportrefs/pull/244/headJaromil2017-02-205-25/+61
| |\ | |/ |/|
* | Merge pull request #248 from mesbahamin/open_read_onlyJaromil2017-02-182-4/+30
|\ \ | | | | | | Open non-writable Tomb files with "read only " mount option
| * | Skip writable check when mounting with "ro" option.refs/pull/248/headAmin Mesbah2017-02-131-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | When opening a tomb file with "ro" passed through the -o option, the writability check in is-valid-tomb() is skipped. This allows tomb files to be opened without write permission. test-open-read-only() now succeeds.
| * | Add failing test for opening read-only tomb.Amin Mesbah2017-02-131-3/+28
| | | | | | | | | | | | | | | | | | | | | | | | Adds a test function called test-open-read-only(). The test prepares a tomb file, removes the "write" permissions from it, and then attempts to open it with "read-only" mount options (`-o ro,noatime,nodev`). The test currently fails as expected.
* | | Merge pull request #245 from Arusekk/masterJaromil2017-02-141-12/+12
|\ \ \ | |/ / |/| | Totally fixed spaces handling in tomb and tomber
| * | Fixed spaces handling in Tombrefs/pull/245/headArusekk2017-02-101-12/+12
| | |
* | | Merge pull request #246 from Narrat/bug/slamJaromil2017-02-091-1/+1
|\ \ \ | | | | | | | | lsof should be correctly detected now
| * | | lsof should be correctly detected nowrefs/pull/246/headNarrat2017-02-071-1/+1
|/ / / | | | | | | | | | LSOF would be set everytime otherwise
* | | Merge pull request #243 from Narrat/bug/slamJaromil2017-02-064-8/+16
|\ \ \ | |/ / |/| | Use of lsof to fix slam for specific mountpoint
| * | Make lsof an optional deprefs/pull/243/headNarrat2017-02-054-5/+12
| | | | | | | | | | | | | | | | | | | | | tomb doesn't need lsof for anything else, and can work regulary without it. So make it an optional feature, which allows to slam a tomb if lsof is installed Updates additionally the man page and generates a new pdf from it
| * | Use of lsof to fix slam for specific mountpointNarrat2017-02-032-4/+5
|/ / | | | | | | | | | | | | | | | | | | Apparantly fuser didn't report back, if the tomb was mounted in a subdir of /run (whereas /run itself is often a tmpfs mount). With no list of process ids those couldn't be killed, so slamming the tomb failed. lsof is capable to report back the sought information. Fixes #220 Additionally fixing the debug output, where a hardcoded mountpoint was used
| * Use --hidden-recipient by default instead of --recipient.Alexandre Pujol2017-02-091-4/+15
| | | | | | | | | | | | Due to the hidden-recipient, GPG will try all the available keys. User can speed up this process providing the recipent using the -r option. Therefore, 'tomb open' optionaly support the -r option.
| * Fix is_valid_recipients private key detectionAlexandre Pujol2017-02-091-1/+1
| |
| * Add -g/--gpgkey option to tell tomb to use GPG key to encrypt a tomb keyAlexandre Pujol2017-02-092-50/+43
| | | | | | | | | | Option -r is now only used to provide the recipient Option -R removed, the new recipient can be given by the -r option.
| * Update the man page with GPG key supportAlexandre Pujol2017-02-031-6/+37
| |
| * Add new options description in tomb -hAlexandre Pujol2017-02-031-0/+3
| |
| * Update function comments & description with GPG recipient support.Alexandre Pujol2017-02-031-3/+6
| |
| * Add support for GPG key in the tomb outputs.Alexandre Pujol2017-02-031-10/+33
| |
| * Allow opening a tomb without giving a valid recipient.Alexandre Pujol2017-02-031-1/+1
| | | | | | | | | | | | | | The -r option always requires an arguments. However GPG does not need any recipient when decrypting a key. In order to be able to open a tomb without writing (the long) recipient, the user can use the -f option to short-cut the valid recipient checking. A dummy recipient is still required.
| * Add '--shared' in order to activate sharing support.Alexandre Pujol2017-02-032-7/+28
| | | | | | | | | | | | | | Sharing feature is a very sensitive action, the user needs to trust the GPG public key it is going to share its tomb. This is why this feature needs to be explicitly activated using in more the flag --shared on the key encryption commands.
| * Add sharing support for tomb key.Alexandre Pujol2017-02-032-13/+82
| | | | | | | | | | | | | | | | A tomb key can be encrypted with more than one recipient. Therefore, a tomb can be shared between different user. The multiple recipients are given using the -r (or/and -R) option and must be separated by ','. Multiple recipients can be given for the commands: forge, setket and passwd
| * Add tomb setkey support for GPG keyAlexandre Pujol2017-02-032-3/+16
| |
| * Add tomb resize support for GPG keyAlexandre Pujol2017-02-032-2/+6
| |
| * Add support to change the GPG key used to encrypt a tomb key. (tomb passwd)Alexandre Pujol2017-02-032-3/+18
| |
| * Improve key encryption/decryption using GPG key.Alexandre Pujol2017-02-031-27/+42
| | | | | | | | | | | | | | | | Decryption/Encryption works without these improvment, however, there are needed in order to have clean key (without empty line). Moreover, tests showed not doing cause troubles when changing the GPG key used to encrypt a tomb key.
| * Improve exhumation of key when opening a tombAlexandre Pujol2017-02-031-12/+14
| |
| * Add --tomb-pwd support for GPG key on steganography functionsAlexandre Pujol2017-02-032-11/+16
| |
| * Add unit tests for steganography feature using GPG keyAlexandre Pujol2017-02-031-1/+29
| |