gocryptfs/internal, branch v1.3-beta1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.3-beta1 2017-03-18T15:48:28+00:00 fusefrontend: get rid of leftover debug output 2017-03-18T15:48:28+00:00 Jakob Unterwurzacher 2017-03-18T15:48:28+00:00 urn:sha1:cb47f65212801fbdd999674e549921d8cf23f2f2 serialize_reads: add read serialization logic 2017-03-18T15:18:00+00:00 Jakob Unterwurzacher 2017-03-18T15:01:50+00:00 urn:sha1:00df0771e3dd9fba0992cbc9a7d347f25aff856a Due to kernel readahead, we usually get multiple read requests at the same time. These get submitted to the backing storage in random order, which is a problem if seeking is very expensive. Details: https://github.com/rfjakob/gocryptfs/issues/92 fusefrontend: readFileID: reject files that consist only of a header 2017-03-12T20:11:02+00:00 Jakob Unterwurzacher 2017-03-12T20:11:02+00:00 urn:sha1:14038a1644f17f50b113a05d09a2a0a3b3e973b2 A header-only file will be considered empty (this is not supposed to happen). This makes File ID poisoning more difficult. fusefrontend: truncateGrowFile: avoid createHeader() call 2017-03-12T20:06:59+00:00 Jakob Unterwurzacher 2017-03-12T20:06:59+00:00 urn:sha1:d36d53c9bbf1b1f1c34578d443770672528e4466 ...if doWrite() can do it for us. This avoids the situation that the file only consists of a file header when calling doWrite. A later patch will check for this condition and warn about it, as with this change it should no longer occour in normal operation. configfile: HKDF feature flag should also be set for "-plaintextnames" 2017-03-07T20:05:45+00:00 Jakob Unterwurzacher 2017-03-07T20:03:05+00:00 urn:sha1:9a0808b1ee4cca94a3178b14838b558bf03d483b contentenc: catch integer underflow in file size calculation 2017-03-07T19:56:50+00:00 Jakob Unterwurzacher 2017-03-06T22:50:17+00:00 urn:sha1:2f953fdb95f44078895fec9bc4d542cd371126be If you truncate a ciphertext file to 19 bytes, you could get the impression that the plaintext is 18446744073709551585 bytes long, as reported by "ls -l". Fix it by clamping the value to zero. configfile: enable HKDF and Raw64 feature flags by default 2017-03-07T19:56:50+00:00 Jakob Unterwurzacher 2017-03-06T21:20:28+00:00 urn:sha1:9f17a78b4a63d7ab5b7e09c294a483c8b806aa49 Also adds a test to verify that they are set in new config files. Report correct symbolic link dentry sizes 2017-03-07T19:46:58+00:00 M. Vefa Bicakci 2017-03-07T09:09:09+00:00 urn:sha1:d48ccb3ddab71773a991b8f1b062901ff5b435b0 Prior to this commit, gocryptfs's reverse mode did not report correct directory entry sizes for symbolic links, where the dentry size needs to be the same as the length of a string containing the target path. This commit corrects this issue and adds a test case to verify the correctness of the implementation. This issue was discovered during the use of a strict file copying program on a reverse-mounted gocryptfs file system. tests: configfile: fix spurious test failure II 2017-03-05T22:24:47+00:00 Jakob Unterwurzacher 2017-03-05T22:24:47+00:00 urn:sha1:6e9b6e17c33b4471c30248c11b292468fe4ab912 internal/configfile/config_test.go:67: c declared and not used tests: configfile: fix spurious test failure 2017-03-05T22:15:50+00:00 Jakob Unterwurzacher 2017-03-05T22:15:50+00:00 urn:sha1:b878306d2a3fd18d4114a73febb2caa658f684ad This test fails because Raw64 has been disabled for now.