gocryptfs/internal/nametransform, branch v1.2 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.2 2016-11-28T22:09:47+00:00 fusefronted: preserve owner for device nodes and sockets 2016-11-28T22:09:47+00:00 Jakob Unterwurzacher 2016-11-28T22:09:47+00:00 urn:sha1:e3c5e3f1c8db31e62bbb781a238da4cf76ed1ffc https://github.com/rfjakob/gocryptfs/issues/64 Fix golint warnings 2016-11-09T23:38:01+00:00 Jakob Unterwurzacher 2016-11-09T23:38:01+00:00 urn:sha1:e7f57695a6c7b3ed545793347506907c7aec3ecc $ golint ./... | grep -v underscore | grep -v ALL_CAPS internal/fusefrontend_reverse/rfs.go:52:36: exported func NewFS returns unexported type *fusefrontend_reverse.reverseFS, which can be annoying to use internal/nametransform/raw64_go1.5.go:10:2: exported const HaveRaw64 should have comment (or a comment on this block) or be unexported nametransform: get rid of leading "./" 2016-11-09T22:41:47+00:00 Jakob Unterwurzacher 2016-11-09T22:41:47+00:00 urn:sha1:df28fc5a11f5e52897f45cc299ab62a2a2cbaf4c Paths in the root directory were encrypted to this: foobar -> ./N9vPc0gXUY4PDSt0-muYXQ== nametransform: nicer error message on empty gocryptfs.diriv 2016-11-06T13:09:34+00:00 Jakob Unterwurzacher 2016-11-06T13:09:34+00:00 urn:sha1:df1e3a10c45cefb393a350f75ebf3fbb8117ef2f Old: Nov 06 13:34:38 brikett gocryptfs[16228]: ReadDirIVAt: Read failed: EOF Nov 06 13:34:38 brikett gocryptfs[16228]: go-fuse: can't convert error type: EOF New: Nov 06 14:08:43 brikett gocryptfs[17361]: ReadDirIVAt: wanted 16 bytes, got 0. Returning EINVAL. Add Go 1.4 compatibility layer for raw64 2016-11-01T18:25:59+00:00 Jakob Unterwurzacher 2016-11-01T18:20:55+00:00 urn:sha1:d15122d3d6b67d42617ed9950ce5273d0dba64fd Using raw64 will not work, but at least it will compile. Add support for unpadded base64 filenames, "-raw64" 2016-11-01T17:43:22+00:00 Jakob Unterwurzacher 2016-11-01T17:43:22+00:00 urn:sha1:2b991c9743caa5edf38fbcdadb129ca61ffa702f Through base64.RawURLEncoding. New command-line parameter "-raw64". fusefronted: expire dir IV cache after one second 2016-11-01T09:57:39+00:00 Jakob Unterwurzacher 2016-11-01T09:57:39+00:00 urn:sha1:944eaf2fb507265d41db5685b1c8d902e20e52da The Back In Time backup tool (https://github.com/bit-team/backintime) wants to write directly into the ciphertext dir. This may cause the cached directory IV to become out-of-date. Having an expiry time limits the inconstency to one second, like attr_timeout does for the kernel getattr cache. fusefrontend: refactor dirIVCache 2016-11-01T09:34:41+00:00 Jakob Unterwurzacher 2016-11-01T09:34:41+00:00 urn:sha1:a9c7565b8002a98f7dc77dfd675ecf1c803fe6b5 Simplify the code a bit. Fix misspellings 2016-10-24T17:18:13+00:00 Jakob Unterwurzacher 2016-10-24T17:18:13+00:00 urn:sha1:aeda9721d0150b9b77d9522bb3b4fcd17f2cbbfa Close https://github.com/rfjakob/gocryptfs/issues/54 nametransform: better error code on invalid diriv length 2016-10-07T20:40:30+00:00 Jakob Unterwurzacher 2016-10-07T20:36:29+00:00 urn:sha1:53257f4ee57cc59e6638b2a6d8a73203b7d99de5 go-fuse translates errors unknown to it into "function not implemented", which is wrong in this case.