gocryptfs/internal/contentenc, branch det Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=det 2017-05-28T18:44:54+00:00 fusefrontend: aessiv: enable deterministiv file id and block iv 2017-05-28T18:44:54+00:00 Jakob Unterwurzacher 2017-05-28T18:44:54+00:00 urn:sha1:791c78b203be199960274053ea2b1d44c63b07c6 Seems to work ok: $ echo aaaaaaaaaaaaaaaaaaa > b/foo $ gocryptfs-xray a/LAh7EiK-kjleJhStVZ1JGg Header: Version: 2, Id: 8d76d368438112fb00cb807fa8210a74 Block 0: IV: b05bb152f77816678230885d09a4a596, Tag: c1c7d580fe01dd1eb543efd9d8eda8ad, Offset: 18 Len: 52 $ > b/foo $ echo aaaaaaaaaaaaaaaaaaa > b/foo $ gocryptfs-xray a/LAh7EiK-kjleJhStVZ1JGg Header: Version: 2, Id: 8d76d368438112fb00cb807fa8210a74 Block 0: IV: b05bb152f77816678230885d09a4a596, Tag: c1c7d580fe01dd1eb543efd9d8eda8ad, Offset: 18 Len: 52 Deterministic diriv generation is still missing. Part of https://github.com/rfjakob/gocryptfs/issues/108 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. full stack: implement HKDF support 2017-03-05T20:59:55+00:00 Jakob Unterwurzacher 2017-03-05T20:59:55+00:00 urn:sha1:d0bc7970f721cee607d993406d97d32e2c660abe ...but keep it disabled by default for new filesystems. We are still missing an example filesystem and CLI arguments to explicitely enable and disable it. configfile: switch to 128-bit IVs for master key encryption 2017-03-05T17:03:03+00:00 Jakob Unterwurzacher 2017-03-05T17:03:03+00:00 urn:sha1:b7328815183b7a4ff37156085fb78e8e86aff165 There is no security reason for doing this, but it will allow to consolidate the code once we drop compatibility with gocryptfs v1.2 (and earlier) filesystems. Replace all calls to naked panic() with log.Panic() 2016-12-10T10:54:36+00:00 Jakob Unterwurzacher 2016-12-10T10:50:16+00:00 urn:sha1:c9f4400e6dc71a36df5dc9725f52a8968f5f9803 We want all panics to show up in the syslog.