gocryptfs/internal/contentenc, branch v1.4 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4 2017-06-11T19:56:16+00:00 contentenc: parallelize encryption for 128kiB writes 2017-06-11T19:56:16+00:00 Jakob Unterwurzacher 2017-06-11T11:34:46+00:00 urn:sha1:e52594dae67a5f2532a2e65abaafc8c993fb2db4 128kiB = 32 x 4kiB pages is the maximum we get from the kernel. Splitting up smaller writes is probably not worth it. Parallelism is limited to two for now. contentenc: move EncryptBlocks() loop into its own functions 2017-06-07T20:09:15+00:00 Jakob Unterwurzacher 2017-06-07T20:06:28+00:00 urn:sha1:294628b38435698ec63f2b13044ec993af1563f1 This allows easy parallelization in the future. fusefrontend: write: consolidate and move encryption to contentenc 2017-06-01T20:19:27+00:00 Jakob Unterwurzacher 2017-06-01T19:39:47+00:00 urn:sha1:a24faa3ba52c66dfc1707da5c8d001f2adff9ccc Collect all the plaintext and pass everything to contentenc in one call. This will allow easier parallization of the encryption. https://github.com/rfjakob/gocryptfs/issues/116 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. contenenc: reject all-zero file ID 2017-05-25T12:20:27+00:00 Jakob Unterwurzacher 2017-05-25T12:20:17+00:00 urn:sha1:2ce269ec63e0a9c87b2fce45a5bf0cf09abf5bba This should never happen in normal operation and is a sign of data corruption. Catch it early. contentenc: better error reporting in ParseHeader 2017-05-25T12:18:44+00:00 Jakob Unterwurzacher 2017-05-25T12:18:44+00:00 urn:sha1:c0e411f81d01607fa59338365933232231738581 Log the message ourselves and return EINVAL. Before: gocryptfs[26962]: go-fuse: can't convert error type: ParseHeader: invalid version: got 0, want 2 After: gocryptfs[617]: ParseHeader: invalid version: want 2, got 0. Returning EINVAL. contentenc: downgrade "interrupted write?" warning to debug 2017-05-01T16:44:18+00:00 Jakob Unterwurzacher 2017-05-01T16:44:18+00:00 urn:sha1:1a89919d80f28ca4126d70bcc1d617145abc2695 This can happen during normal operation, and is harmless since 14038a1644f17f50b113a05d09a2a0a3b3e973b2 "fusefrontend: readFileID: reject files that consist only of a header" causes dormant header-only files to be rewritten on the next write. forcedecode: tighten checks 2017-04-23T22:25:02+00:00 Jakob Unterwurzacher 2017-04-23T22:25:02+00:00 urn:sha1:3409ade2723d931097560fbbe35e461553c5912c ...and fix a few golint issues and print a scary warning message on mount. Also, force the fs to ro,noexec. Add -forcedecode 2017-04-23T21:11:56+00:00 danim7 2017-04-08T00:09:28+00:00 urn:sha1:f1945c4daae65074cfca8f0ab5b97ac5a50c24a0 Force decode of encrypted files even if the integrity check fails, instead of failing with an IO error. Warning messages are still printed to syslog if corrupted files are encountered. It can be useful to recover files from disks with bad sectors or other corrupted media. Closes https://github.com/rfjakob/gocryptfs/pull/102 . 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.