gocryptfs/internal/fusefrontend_reverse, branch v1.7-beta1Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.7-beta12018-09-08T16:06:33+00:00syscallcompat: use O_PATH in OpenDirNofollow2018-09-08T16:06:33+00:00Jakob Unterwurzacher2018-09-08T16:06:33+00:00urn:sha1:930c37e03d5ff80e7cdc9f0ca2cd35d80a06d5c0
This fixes the "0100 directory" problem in reverse mode,
and should be slightly faster.
syscallcompat: untangle OpenNofollow and rename to OpenDirNofollow2018-09-08T15:41:17+00:00Jakob Unterwurzacher2018-09-08T15:41:17+00:00urn:sha1:9ec9d0c49cfbdc9ceba10d7534b77e527c0a3cdc
The function used to do two things:
1) Walk the directory tree in a manner safe from symlink attacks
2) Open the final component in the mode requested by the caller
This change drops (2), which was only used once, and lets the caller
handle it. This simplifies the function and makes it fit for reuse in
forward mode in openBackingPath(), and for using O_PATH on Linux.
fusefrontend_reverse: reject excludes for the root directory ""2018-08-15T10:28:29+00:00Jakob Unterwurzacher2018-08-15T10:28:29+00:00urn:sha1:7a02f71fc2fc8fc104ad1538f417d1e93e73cf11
This is most likely a mistake by the user. Reject it.
reverse mode: add --exclude option2018-08-11T21:26:49+00:00Jakob Unterwurzacher2018-08-11T21:26:49+00:00urn:sha1:ec2fdc19cf9358ae7ba09c528a5807b6b0760f9b
https://github.com/rfjakob/gocryptfs/issues/235
darwin does not have PATH_MAX2018-06-07T22:47:48+00:00Jakob Unterwurzacher2018-06-07T22:47:48+00:00urn:sha1:bde7ba57b06eb46f8901454e12524a74a8c3b6e8
Define our own, with the value from Linux.
fusefrontend[_reverse]: move crypto init up to caller2018-02-18T10:21:58+00:00Jakob Unterwurzacher2018-02-17T15:26:35+00:00urn:sha1:719693ec5dd1153318606f151915231d71ddfe0b
Both fusefrontend and fusefrontend_reverse were doing
essentially the same thing, move it into main's
initFuseFrontend.
A side-effect is that we have a reference to cryptocore
in main, which will help with wiping the keys on exit
(https://github.com/rfjakob/gocryptfs/issues/211).
gccgo: replace syscall.NAME_MAX with unix.NAME_MAX2018-02-01T22:50:11+00:00Jakob Unterwurzacher2018-02-01T22:46:02+00:00urn:sha1:9f8d0d8e5734e3771b52c8a8784ef5a76b0f9ca8
For some reason the syscall.NAME_MAX constant does not exist
on gccgo, and it does not hurt us to use unix.NAME_MAX instead.
https://github.com/rfjakob/gocryptfs/issues/201
fusefrontend_reverse: use OpenNofollow in virtualFile.GetAttr2018-01-17T20:36:38+00:00Jakob Unterwurzacher2018-01-17T20:36:38+00:00urn:sha1:a2677bce2a632d80850fabb1e397558d8a07742b
Makes it robust against symlink races.
Final piece, closes https://github.com/rfjakob/gocryptfs/issues/165
fusefrontend_reverse: use OpenNofollow in findLongnameParent2018-01-17T19:54:05+00:00Jakob Unterwurzacher2018-01-17T19:52:52+00:00urn:sha1:959e1fc1e2f531480ad1353179fc94f56ff76dce
Protects findLongnameParent against symlink races.
Also add comments to several functions along the way.
Reported at https://github.com/rfjakob/gocryptfs/issues/165
Run go fmt2018-01-16T22:18:53+00:00Jakob Unterwurzacher2018-01-16T22:16:54+00:00urn:sha1:36ffd813cd04c6c43a7572ba5d71db4da8c2b060