gocryptfs/daemonize.go, branch xattr_user_bufferMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer2024-05-17T20:14:37+00:00daemonize: fix typo in comment2024-05-17T20:14:37+00:00Jakob Unterwurzacher2024-05-17T20:14:37+00:00urn:sha1:72ec4b005bdf2ee54945485dbd3a8bc07ef3d454go mod: declare module version v22021-08-23T13:05:15+00:00Jakob Unterwurzacher2021-08-23T13:05:15+00:00urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858
Our git version is v2+ for some time now, but go.mod
still declared v1. Hopefully making both match makes
https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work.
All the import paths have been fixed like this:
find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/%
main: drop hardcoded /usr/bin/logger path2018-11-17T16:03:11+00:00Jakob Unterwurzacher2018-11-17T16:03:11+00:00urn:sha1:d882ed45da9464e0e244cd8a3bf0168b5b618fd9
The hardcoded full paths were introduced to handle the
case of an empty PATH environment variable. However,
since commit 10212d791a3196c2c870 we set PATH to a default
value if empty. The hardcoded paths are no longer neccessary,
and cause problems on some distros:
User voobscout on
https://github.com/rfjakob/gocryptfs/issues/225#issuecomment-438682034 :
just to chime in - please don't hardcode paths, for example I'm on
NixOS and logger lives in /run/current-system/sw/bin/logger
Drop the hardcoded paths.
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.
main: forkChild: try to read /proc/self/exe2018-06-07T21:09:27+00:00Jakob Unterwurzacher2018-06-07T21:06:03+00:00urn:sha1:fb772da6975eec186161fb00ededc2aef43f9eb9
On Linux, where /proc exists, this makes sure that we are
executing ourselves again, and not some other copy of the
gocryptfs executable.
This usually does not matter, but mount(1) unsets $PATH
and sets argv[0] to just "gocryptfs".
main: accept -dev, -nodev, -suid, -nosuid, -exec, -noexec2018-06-07T20:50:30+00:00Jakob Unterwurzacher2018-06-07T20:50:30+00:00urn:sha1:53d6a9999dd0e4c31636d16179f284fff35a35d9
When mounted via /etc/fstab like this,
/a /b fuse.gocryptfs default 0 0
we always get extra options passed. As reported by @mahkoh
at https://github.com/rfjakob/gocryptfs/pull/233 :
mount passes `-o noexec` if `-o user` is set and `-o exec` is not set.
If both `-o user` and `-o exec` are set, it passes `-o exec`.
Make these options work, and in addtion, also make -suid and -rw
work the same way.
Reported-by: @mahkoh
daemonize: try /bin/logger if /usr/bin/logger fails2018-04-11T18:31:02+00:00Jakob Unterwurzacher2018-04-11T18:31:02+00:00urn:sha1:12832851c68ce6ba2907b5d5fefc2a5e49f7c36a
SUSE has /bin/logger, everybody else has /usr/bin/logger,
so try both.
Fixes https://github.com/rfjakob/gocryptfs/issues/225
main: call logger with full path2017-10-18T18:25:34+00:00Jakob Unterwurzacher2017-10-18T18:23:50+00:00urn:sha1:2783eadc8f69ae5803a75dbfccd7ea1862cdfe51
If $PATH contains the mountpoint, searching through it
will lock us up. Use an absolute path to avoid looking
at $PATH.
Fixes https://github.com/rfjakob/gocryptfs/issues/146
main: redirectStdFds: keep logger from holding stdout open2017-07-23T22:05:39+00:00Jakob Unterwurzacher2017-07-23T21:55:59+00:00urn:sha1:496968e06c09f896ed04ad0939242e1ae75cde53
We passed our stdout and stderr to the new logger instance,
which makes sense to see any error message, but also means that
the fd is kept open even when we close it.
Fixes the new TestMountBackground test and
https://github.com/rfjakob/gocryptfs/issues/130 .
main: move redirectStdFds() to daemonize.go2017-07-23T17:21:23+00:00Jakob Unterwurzacher2017-07-23T17:18:58+00:00urn:sha1:0b6e3ce635ed7a9ec592f0cb72bc1afe7b9ed23e
This really is a part of daemonization.
No code changes.