gocryptfs/internal, branch v1.3 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.3 2017-04-29T16:20:39+00:00 fusefronted: drop unused file.String() function 2017-04-29T16:20:39+00:00 Jakob Unterwurzacher 2017-04-29T16:20:39+00:00 urn:sha1:b66e03486a9839d3422931f81c70ada8fc4a8b4d This is a very old leftover. readpassword: increase max password size to 2048 2017-04-29T13:15:11+00:00 Jakob Unterwurzacher 2017-04-29T13:15:11+00:00 urn:sha1:6e029a3799816dd6703b2cb573022c7c3fd15c39 This is the value EncFS uses, so let's follow suit. Suggested at https://github.com/rfjakob/gocryptfs/issues/77 . fix golint complaints 2017-04-29T12:50:58+00:00 Jakob Unterwurzacher 2017-04-29T12:50:58+00:00 urn:sha1:edb3e19cb5543c580261052395d461fa47c7cf58 nametransform: WriteDirIV: replace ioutil.WriteFile 2017-04-29T12:15:13+00:00 Jakob Unterwurzacher 2017-04-29T12:15:13+00:00 urn:sha1:7d38f80a78644c8ec4900cc990bfb894387112ed As reported at https://github.com/rfjakob/gocryptfs/issues/105 , the "ioutil.WriteFile(file, iv, 0400)" call causes "permissions denied" errors on an NFSv4 setup. "strace"ing diriv creation and gocryptfs.conf creation shows this: conf (works on the user's NFSv4 mount): openat(AT_FDCWD, "/tmp/a/gocryptfs.conf.tmp", O_WRONLY|O_CREAT|O_EXCL|O_CLOEXEC, 0400) = 3 diriv (fails): openat(AT_FDCWD, "/tmp/a/gocryptfs.diriv", O_WRONLY|O_CREAT|O_TRUNC|O_CLOEXEC, 0400) = 3 This patch creates the diriv file with the same flags that are used for creating the conf: openat(AT_FDCWD, "/tmp/a/gocryptfs.diriv", O_WRONLY|O_CREAT|O_EXCL|O_CLOEXEC, 0400) = 3 Closes https://github.com/rfjakob/gocryptfs/issues/105 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 . Fix Flock build breakage 2017-04-22T22:06:56+00:00 Jakob Unterwurzacher 2017-04-22T22:06:56+00:00 urn:sha1:9777e4bf7ea2aa75ab443dc6e15c42103eb6b027 go-fuse has added a new method to the nodefs.File interface that caused this build error: internal/fusefrontend/file.go:75: cannot use file literal (type *file) as type nodefs.File in return argument: *file does not implement nodefs.File (missing Flock method) Fixes https://github.com/rfjakob/gocryptfs/issues/104 and prevents the problem from happening again. fusefrontend_reverse: switch to stable inode numbers 2017-04-01T15:19:15+00:00 Jakob Unterwurzacher 2017-04-01T15:19:15+00:00 urn:sha1:778c955eea1fdc16666f51f6f0a2fab0f580dbf0 The volatile inode numbers that we used before cause "find" to complain and error out. Virtual inode numbers are derived from their parent file inode number by adding 10^19, which is hopefully large enough no never cause problems in practice. If the backing directory contains inode numbers higher than that, stat() on these files will return EOVERFLOW. Example directory lising after this change: $ ls -i 926473 gocryptfs.conf 1000000000000926466 gocryptfs.diriv 944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA 1000000000000944878 gocryptfs.longname.hmZojMqC6ns47eyVxLlH2ailKjN9bxfosi3C-FR8mjA.name 934408 Tdfbf02CKsTaGVYnAsSypA fusefrontend_reverse: drop unused dirIVAttr function 2017-04-01T15:05:55+00:00 Jakob Unterwurzacher 2017-04-01T15:05:55+00:00 urn:sha1:e87aebb835b91ba66f288030ee3510df42b860a9 This has long been replaced by virtualFile.GetAttr(). fusefrontend_reverse: convert fmt.Printf calls to tlog 2017-04-01T13:49:53+00:00 Jakob Unterwurzacher 2017-04-01T13:49:53+00:00 urn:sha1:acb73ca4363a8fbf3e0be1907a9b26689d879d73 The fmt.Printfs output would end up in the paniclog.