gocryptfs/mount.go, branch v2.6.0 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.6.0 2025-06-05T17:31:29+00:00 mount: fix -force_owner not allowing file/dir create 2025-06-05T17:31:29+00:00 Jakob Unterwurzacher 2025-06-05T17:31:29+00:00 urn:sha1:4358a9f998d469bf6aac077d76847498710c6b42 Fixes https://github.com/rfjakob/gocryptfs/issues/783 idleMonitor: switch to the new atomic.Bool api 2025-05-29T19:38:25+00:00 Jakob Unterwurzacher 2025-05-29T19:30:53+00:00 urn:sha1:2609c72beee098c6afe4bbc3344a1fcee06df94b cli: mount: add -context option 2025-04-19T17:42:28+00:00 Jakob Unterwurzacher 2025-04-19T17:39:10+00:00 urn:sha1:6918a4413decccd2f535e66d12b2e3dee10a74a8 Set the SELinux context. See mount(8) for details. Report inode number for the root node 2024-11-11T21:33:07+00:00 Jakob Unterwurzacher 2024-11-11T21:27:42+00:00 urn:sha1:86891054ef2a5d1b0b59c7c140aae284e7c5bd87 Now that https://github.com/hanwen/go-fuse/issues/399 has landed we can report an inode number for the root node. Fixes https://github.com/rfjakob/gocryptfs/issues/580 ctlsocksrv: move Listen() call here 2024-09-02T14:31:23+00:00 Jakob Unterwurzacher 2024-09-02T14:31:23+00:00 urn:sha1:40abf968eddd54b6c03ac064d6e42cc6f1083146 Prep for solving https://github.com/rfjakob/gocryptfs/issues/776 cli: deduplicate kernel options 2024-07-27T19:05:00+00:00 Joker 2024-06-15T10:04:03+00:00 urn:sha1:533c9eb7cedeaaa23d0901d703e1c416b0fd0151 Merge stock kernel options with user-provided ones before passing to go-fuse. Before: `-ko volname=custom` would result in `-o volname=mountpoint,volname=custom` to macFUSE. After: `-ko volname=custom` would produce `-o volname=custom` with no duplicates. Fixes #854 and #557 mount: set DirectMount: true 2023-05-17T14:47:22+00:00 Jakob Unterwurzacher 2023-05-17T14:47:22+00:00 urn:sha1:a40e9a8622b0d79ba0c18361104c47375ebb89a1 Attempt to directly call mount(2) before trying fusermount. This means we can do without fusermount if running as root. https://github.com/rfjakob/gocryptfs/issues/697 mount: drop "max_read=" 2023-05-17T13:48:23+00:00 Jakob Unterwurzacher 2023-05-17T13:37:11+00:00 urn:sha1:b4defa636b901d992165e2a828872dd410c48292 go-fuse now sets this internally. Regression-tested in TestDirectMount. mount: set FsName via go-fuse 2023-05-17T13:38:35+00:00 Jakob Unterwurzacher 2023-05-17T13:35:01+00:00 urn:sha1:199a74bc1ae49cdda486095b8daa8034510943a6 go-fuse now handles setting FsName, including DirectMount, so use that instead of our own solution. Regression-tested in TestDirectMount. main: doMount: call Setsid before starting logger 2022-12-29T12:57:03+00:00 Jakob Unterwurzacher 2022-12-29T12:52:35+00:00 urn:sha1:ff32e9979130e6237b0d97ef88304fa79ce61b06 The logger should be in the new background session together with the gocryptfs process. Before: $ xfce4-terminal -x gocryptfs a b $ ps xao pid,ppid,pgid,sid,comm,args PID PPID PGID SID COMMAND COMMAND 192272 1371 192272 192272 gocryptfs /ssd2/jakob.donotbackup/go/bin/gocryptfs -fg -notifypid=192265 a b 192292 192272 192265 192265 logge <defunct> [logger] <defunct> After: $ xfce4-terminal -x gocryptfs a b $ ps xao pid,ppid,pgid,sid,comm,args PID PPID PGID SID COMMAND COMMAND 211714 1371 211714 211714 gocryptfs /ssd2/jakob.donotbackup/go/bin/gocryptfs -fg -notifypid=211708 a b 211776 211714 211714 211714 logger logger -t gocryptfs-211714-logger Fixes https://github.com/rfjakob/gocryptfs/issues/660