gocryptfs/tests, branch v1.6Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.62018-08-15T11:12:13+00:00main: add -e as an alias for -exclude2018-08-15T11:12:13+00:00Jakob Unterwurzacher2018-08-15T11:11:34+00:00urn:sha1:5acfbc1b2ffbd156ca7a1f2cc09084a518f1d58ereverse mode: add --exclude option2018-08-11T21:26:49+00:00Jakob Unterwurzacher2018-08-11T21:26:49+00:00urn:sha1:ec2fdc19cf9358ae7ba09c528a5807b6b0760f9b
https://github.com/rfjakob/gocryptfs/issues/235
tests: VerifyExistence: panic on inconsistent results2018-08-11T20:37:22+00:00Jakob Unterwurzacher2018-08-11T20:37:22+00:00urn:sha1:06f1ea951b03b4a0e8f6090c6657b8e0238da271
In the past we did not check whether all methods of checking
the file return the same result. We should.
fsck: handle sparse files efficiently, fix xfstests generic/2852018-07-01T19:48:51+00:00Jakob Unterwurzacher2018-07-01T17:14:00+00:00urn:sha1:2d68b06f9dab66b2a0a6c29c8d5450e2b1d43fae
If we encounter a 128KB block of zeros, try to skip to the next
data section by calling File.SeekData().
This fixes xfstests generic/285, which creates a 17TB sparse file,
and runs fsck afterwards. Without this optimization, fsck would
take ages.
trezor: add TrezorPayload2018-07-01T18:56:22+00:00Jakob Unterwurzacher2018-06-25T20:27:15+00:00urn:sha1:9a15dfa494c76b5fcadcd32e2e46cbee84218a87
TrezorPayload stores 32 random bytes used for unlocking
the master key using a Trezor security module. The randomness makes sure
that a unique unlock value is used for each gocryptfs filesystem.
configfile: reduce function name stutter2018-07-01T18:56:22+00:00Jakob Unterwurzacher2018-06-25T20:02:05+00:00urn:sha1:91de77943fba3cb993aad4e9756e159c4514764a
configfile.LoadConfFile() -> configfile.Load()
configfile.CreateConfFile() -> configfile.Create()
trezor: exit with usage error if used together with -extpass2018-07-01T18:56:22+00:00Jakob Unterwurzacher2018-06-25T19:55:20+00:00urn:sha1:8e5ca7299a3292cae64418aaf875819c2cca01f5
Using an external program for the Trezor PIN is not supported
at the moment.
trezor: add basic "-init -trezor" test2018-07-01T18:56:09+00:00Jakob Unterwurzacher2018-06-24T17:53:08+00:00urn:sha1:4bf02f476034f6a30a378769cda323e0ce5ae59f
Verify that the Trezor feature flag is set after "-init -trezor".
trezor: add skeleton for Trezor support2018-07-01T18:56:04+00:00Jakob Unterwurzacher2018-06-17T13:25:09+00:00urn:sha1:c6f6e8ec4d71475a24ebbb0e64f19ad94249efd9
readpassword.Trezor() is not implemented yet and returns
a hardcoded dummy key.
main: accept -dev, -nodev, -suid, -nosuid, -exec, -noexec2018-06-07T20:50:30+00:00Jakob Unterwurzacher2018-06-07T20:50:30+00:00urn:sha1:53d6a9999dd0e4c31636d16179f284fff35a35d9
When mounted via /etc/fstab like this,
/a /b fuse.gocryptfs default 0 0
we always get extra options passed. As reported by @mahkoh
at https://github.com/rfjakob/gocryptfs/pull/233 :
mount passes `-o noexec` if `-o user` is set and `-o exec` is not set.
If both `-o user` and `-o exec` are set, it passes `-o exec`.
Make these options work, and in addtion, also make -suid and -rw
work the same way.
Reported-by: @mahkoh