gocryptfs/tests, branch v1.4 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4 2017-06-01T16:53:57+00:00 Fix two comments 2017-06-01T16:53:57+00:00 Jakob Unterwurzacher 2017-06-01T16:53:57+00:00 urn:sha1:f44902aaaeb8f60060c2f852b66962eca1df6b99 One out-of-date and the other with a typo. tests: add v1.3-reverse example filesystem 2017-05-30T15:04:46+00:00 Jakob Unterwurzacher 2017-05-28T17:02:22+00:00 urn:sha1:e43eb36da3e72cd0f59ac978cf76a94fa87ca7cd We check the md5 sum of the encrypted version of a file to make sure we don't accidentially change the ciphertext generation. main: password change: exit with code 12 on wrong password 2017-05-14T11:14:00+00:00 Jakob Unterwurzacher 2017-05-14T11:14:00+00:00 urn:sha1:18f354d84b4ae58c620474a544b9929662b108d8 We used to return code 8, now we return code 12 as documented in the man page. Also adds a test. exitcodes: pull all exit code definitions into the package 2017-05-07T20:16:22+00:00 Jakob Unterwurzacher 2017-05-07T20:15:01+00:00 urn:sha1:d5adde1eeb13ba377f7c05b9f21893c01f61ec16 This commit defines all exit codes in one place in the exitcodes package. Also, it adds a test to verify the exit code on incorrect password, which is what SiriKali cares about the most. Fixes https://github.com/rfjakob/gocryptfs/issues/77 . fusefrontend: implement path decryption via ctlsock 2017-05-07T19:01:39+00:00 Jakob Unterwurzacher 2017-05-07T19:01:39+00:00 urn:sha1:ad7942f434fea567f24458e67a0919291b5ec8dd Closes https://github.com/rfjakob/gocryptfs/issues/84 . Fix typos found by Misspell 2017-05-07T10:22:15+00:00 Jakob Unterwurzacher 2017-05-07T10:22:15+00:00 urn:sha1:68387b470c0d6d2896cc6b927a6e3097389d66ab Misspell Finds commonly misspelled English words gocryptfs/internal/configfile/scrypt.go Line 41: warning: "paramter" is a misspelling of "parameter" (misspell) gocryptfs/internal/ctlsock/ctlsock_serve.go Line 1: warning: "implementes" is a misspelling of "implements" (misspell) gocryptfs/tests/test_helpers/helpers.go Line 27: warning: "compatability" is a misspelling of "compatibility" (misspell) tests: support encfs in the fsstress script 2017-05-01T21:50:49+00:00 Jakob Unterwurzacher 2017-05-01T21:50:49+00:00 urn:sha1:daada9d7c6207328ad49a4d96050eb08e1a003a1 May be helpful for https://github.com/vgough/encfs/issues/214 . tests: add TestXfs124 2017-05-01T16:44:03+00:00 Jakob Unterwurzacher 2017-05-01T16:36:25+00:00 urn:sha1:9768376bd1961a5aa0fbf7f08de0601322664fc3 This test reproduces the problem xfstests generic/124 uncovered. The warning itself is harmless, but we should either (1) add locking so that this cannot happen anymore or (2) drop the warning. Currently fails: $ go test -v === RUN Test1980Tar --- PASS: Test1980Tar (0.00s) === RUN TestCtlSock --- PASS: TestCtlSock (0.10s) === RUN TestOpenTruncateRead --- PASS: TestOpenTruncateRead (0.00s) === RUN TestWORead --- PASS: TestWORead (0.00s) === RUN TestXfs124 cipherSize 18 == header size: interrupted write? -wpanic turns this warning into a panic: cipherSize 18 == header size: interrupted write? fusefrontend: drop writeOnly flag 2017-05-01T15:49:37+00:00 Jakob Unterwurzacher 2017-05-01T15:49:37+00:00 urn:sha1:9ab11aa4d775f7c1242e8b044cc2f8957cc2c784 We do not have to track the writeOnly status because the kernel will not forward read requests on a write-only FD to us anyway. I have verified this behavoir manually on a 4.10.8 kernel and also added a testcase. tests: add hkdf_sanity tests with broken example filesystem 2017-03-18T15:48:58+00:00 Jakob Unterwurzacher 2017-03-18T15:48:58+00:00 urn:sha1:f1dbd19fe9f277430f4edc1501f4fb5dd8f745b1 These are deliberately corrupt.