gocryptfs/internal/fusefrontend, branch v1.7.1Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7.12019-10-06T19:47:36+00:00fusefrontend: unregister from openfiletable before closing the fd2019-10-06T19:47:36+00:00Jakob Unterwurzacher2019-10-06T19:27:38+00:00urn:sha1:00af4f48643f0533b6cfbd14fdf5186c844f8f5d
Closing the fd means the inode number may be reused immediately
by a new file, so we have to get the old fileID out of the table
beforehand!
Hopefully fixes https://github.com/rfjakob/gocryptfs/issues/363
fusefrontend: print file hexdump on header error2019-10-06T17:37:51+00:00Jakob Unterwurzacher2019-10-06T17:36:04+00:00urn:sha1:43265940fa2d43ebea8edb00373aa4d6718e2ea7
This should help debugging https://github.com/rfjakob/gocryptfs/issues/363 ,
but does no harm in normal operation as it only prints ciphertext to the log.
Fix -idle unmounting despite activity2019-09-08T14:29:20+00:00Jakob Unterwurzacher2019-09-08T14:29:20+00:00urn:sha1:0a4db7d9e9801a416602b52281537991ba1463c0
Fixes https://github.com/rfjakob/gocryptfs/issues/421
fusefrontend: get rid of last hardcoded "gocryptfs.diriv" instances2019-04-09T18:51:33+00:00Jakob Unterwurzacher2019-04-09T18:51:33+00:00urn:sha1:7d81494a649f3f871bfeb4bb129cbfa738fbef67
Makes it easier to change the name (as some people want to):
https://github.com/rfjakob/gocryptfs/issues/37
reverse mode: support wildcard exclude (--exclude-wildcard)2019-03-26T19:56:37+00:00Eduardo M KALINOWSKI2019-02-16T20:55:54+00:00urn:sha1:3bc100aeb3f0763f78c8b3a70165b9f8aaa52db5
This adds support for gitignore-like wildcards and exclude patters in
reverse mode. It (somewhat) fixes #273: no regexp support, but the
syntax should be powerful enough to satisfy most needs.
Also, since adding a lot of --exclude options can be tedious, it adds
the --exclude-from option to read patterns from a file (or files).
nametransform: reject names longer than 255 chars2019-02-17T16:05:05+00:00Jakob Unterwurzacher2019-02-17T16:05:05+00:00urn:sha1:19cb6d046aac92f44722c17ba9a371b08ca0be6a
Looks like we allowed creating longer names by accident.
Fix that, and add a test that verifies it.
fusefronted: comment why Access() does not check context.Uid2019-01-20T13:37:36+00:00Jakob Unterwurzacher2019-01-20T12:34:46+00:00urn:sha1:b08cbce5c1244f901e58812402d82a1816ecf436
https://github.com/rfjakob/gocryptfs/issues/347
fusefrontend: ensure directories without W or X perms can be deleted2019-01-20T13:29:28+00:00Jakob Unterwurzacher2019-01-20T13:29:28+00:00urn:sha1:962c52364415496b64a42b49fe5f90d593dc09f7
This fixed the "Permission denied" bug, but still has the problem that
the directory may be replaced behind our back. Mitigated by the fact
that we skip the workaround when running as root with -allow_other.
https://github.com/rfjakob/gocryptfs/issues/354
Revert "syscallcompat: drop Faccessat AT_SYMLINK_NOFOLLOW helper"2019-01-20T12:10:59+00:00Jakob Unterwurzacher2019-01-20T12:10:59+00:00urn:sha1:3d6b2685fb926b40b4eb528a8cbdc3871444d492
Breaks mounting on MacOS: unix.Faccessat on Darwin does NOT (yet)
support AT_SYMLINK_NOFOLLOW. See d44fe89ba4f3252c5bd00c4f7730197732f2a26a .
This reverts commit 0805a63df1b5f915b228727f6074c2506922d0ad.
syscallcompat: drop Faccessat AT_SYMLINK_NOFOLLOW helper2019-01-20T11:59:59+00:00Jakob Unterwurzacher2019-01-20T11:59:59+00:00urn:sha1:0805a63df1b5f915b228727f6074c2506922d0ad
unix.Faccessat has added support for AT_SYMLINK_NOFOLLOW in July 2018,
https://github.com/golang/sys/commit/bd9dbc187b6e1dacfdd2722a87e83093c2d7bd6e#diff-341484dbbe3180cd7a31ef2ad2d679b6
which means we no longer need our own helper.
Closes https://github.com/rfjakob/gocryptfs/issues/347