gocryptfs/internal/fusefrontend_reverse, branch v1.2 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.2 2016-11-17T19:32:19+00:00 fusefrontend: upgrade wlockMap to use device AND inode number 2016-11-17T19:32:19+00:00 Jakob Unterwurzacher 2016-11-17T19:32:19+00:00 urn:sha1:e04dc050126edcf7440ea5412bc74c6ad8b42e95 If there are multiple filesystems backing the gocryptfs filesystems inode numbers are not guaranteed to be unique. ctlsock: prevent panic on invalid decrypt request 2016-11-10T22:51:47+00:00 Jakob Unterwurzacher 2016-11-10T22:51:47+00:00 urn:sha1:d8fb28a1c38cda0b013c617404ad4a768effb704 ctlsock: implement EncryptPath for reverse mode, add tests 2016-11-10T22:32:51+00:00 Jakob Unterwurzacher 2016-11-10T22:32:51+00:00 urn:sha1:c03fc46a5150715bf6aee20ce4b89d9704141220 reverse: fix longname decoding bug 2016-11-10T22:30:30+00:00 Jakob Unterwurzacher 2016-11-10T22:25:37+00:00 urn:sha1:d3764b775395faa31afb1db34c5c2814a0e9af09 This could have caused spurious ENOENT errors. That it did not cause these errors all the time is interesting and probably because an earlier readdir would place the entry in the cache. This masks the bug. 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 ctlsock: add initial limited implementation 2016-11-09T23:27:08+00:00 Jakob Unterwurzacher 2016-11-09T23:27:08+00:00 urn:sha1:75ebb28a625bc16d145f5acd9e0cc1d305716afe At the moment, in forward mode you can only encrypt paths and in reverse mode you can only decrypt paths. 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". 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 reverse: add panics against API abuse 2016-10-09T15:05:12+00:00 Jakob Unterwurzacher 2016-10-09T15:05:12+00:00 urn:sha1:d3b78fea959dfb0e1c1f5079ae516303bdb9a0f8 These should help prevent later programming errors. reverse: gocryptfs.conf was missing from the directory listings 2016-10-08T20:25:08+00:00 Jakob Unterwurzacher 2016-10-08T20:25:08+00:00 urn:sha1:d25fcc6a4b095e37c77cce8f9de2ec0f12007ed5 Fix the test for that and add checks in example_filesystems_test.