gocryptfs, branch v1.3 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.3 2017-04-29T20:18:28+00:00 README: set release date for v1.3 2017-04-29T20:18:28+00:00 Jakob Unterwurzacher 2017-04-29T20:18:28+00:00 urn:sha1:d20290671e2157162e608c43230fb6c51abfbc94 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 . main: "--" should also block "-o" parsing 2017-04-29T13:11:17+00:00 Jakob Unterwurzacher 2017-04-29T13:11:17+00:00 urn:sha1:e135a72bda6ffa828e5445a16c349dd7017db282 Includes test cases. 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. README: add 64-bit inode numbers to changelog 2017-04-01T18:21:35+00:00 Jakob Unterwurzacher 2017-04-01T18:21:35+00:00 urn:sha1:8ed89a13acc5e9fdf80de975fbb67f485fff8986