gocryptfs, branch v2.5.2 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.2 2025-03-19T15:49:21+00:00 test.bash, crossbuild.bash: drop old Go version kludges 2025-03-19T15:49:21+00:00 Jakob Unterwurzacher 2025-03-19T15:49:21+00:00 urn:sha1:13773f47d6d9aa72da034f2011a84248cbd2f46d GO111MODULE is default on with Go 1.16, same version that gained darwin/arm64 support. We only support Go 1.19 and up, so drop the kludges. README: update changelog 2025-03-19T15:43:18+00:00 Jakob Unterwurzacher 2025-03-19T15:43:18+00:00 urn:sha1:50eb371e9051fbcaef5aeb26198a3fd6b56061db test.bash: catch calls to unix.Seteuid and friends 2025-03-19T15:33:16+00:00 Jakob Unterwurzacher 2025-03-19T15:33:16+00:00 urn:sha1:34be08a1aa2b00784719d614f0f84f7f02bae2f1 https://github.com/rfjakob/gocryptfs/issues/893 github ci: clean up Go versions 2025-03-11T22:25:32+00:00 Jakob Unterwurzacher 2025-03-11T22:25:32+00:00 urn:sha1:106470d940f7d9fa584463c92f7b2f4f51bce215 go-libaegis does not support Go 1.18, Ubuntu 22.04 is old, drop it. github ci: bump nmount_max and print resulting fuse.conf 2025-03-11T22:25:04+00:00 Jakob Unterwurzacher 2025-03-11T22:12:22+00:00 urn:sha1:1c335c73545fbddd83fc905925e808f01cb851a0 We have been getting /usr/bin/fusermount3: too many FUSE filesystems mounted; mount_max=N can be set in /etc/fuse.conf fs.Mount failed: fusermount exited with code 256 every now and then. I wonder why that is. go.mod: upgrade to golang.org/x/crypto@v0.33.0 2025-03-01T19:54:10+00:00 Jakob Unterwurzacher 2025-03-01T19:54:10+00:00 urn:sha1:6cf295e0e13ec21b207bdf1309907e7c43b33726 I did NOT upgrade to x/crypto@v0.35.0 yet because this requires go 1.23.0 (https://go.googlesource.com/crypto/+/89ff08d67c4d79f9ac619aaf1f7388888798651f) and our github workflow tests go 1.18.x and newer. go.mod: upgrade golang.org/x/sys 2025-02-26T21:01:13+00:00 Jakob Unterwurzacher 2025-02-26T21:00:03+00:00 urn:sha1:ec506e501fa39b65083f405b25c2af0d8875ef7a Now that we have our own wrappers for Setreuid and friends, we can upgrade. $ go get golang.org/x/sys go: upgraded golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a => v0.30.0 $ go mod tidy tests/root_test: use our own Setgroups/Setregid/Setreuid wrappers 2025-02-26T20:56:25+00:00 Jakob Unterwurzacher 2025-02-26T20:56:25+00:00 urn:sha1:0024b056d668290e5105527e8ff0a3b23a3a70c8 syscallcompat: use our own Setgroups/Setregid/Setreuid wrappers 2025-02-26T20:38:36+00:00 Jakob Unterwurzacher 2025-02-26T20:38:36+00:00 urn:sha1:6b1ba5846b17eec710a70cb6c6bf23e3f2024289 x/sys v0.1.0 (https://github.com/golang/sys/commit/d0df966e6959f00dc1c74363e537872647352d51) breaks our usecase. Switch to our own wrappers. Relates-to: https://github.com/rfjakob/gocryptfs/issues/892 Relates-to: https://github.com/rfjakob/gocryptfs/issues/893 syscallcompat: add docs for Setreuid/Setregid/Setgroups 2025-02-26T20:33:06+00:00 Jakob Unterwurzacher 2025-02-26T20:32:53+00:00 urn:sha1:07b1bd7ce810c83ed622885b65dbba3dab0f7fbb