gocryptfs, branch v2.5.3Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.32025-04-05T10:24:50+00:00Update changelog2025-04-05T10:24:50+00:00Jakob Unterwurzacher2025-04-05T10:24:50+00:00urn:sha1:31f17432bfdf8bd9ca93f7a18b494d13d019d862tests: fsck: generate evil files with "\r" and "\n" on the fly2025-04-05T09:46:07+00:00Jakob Unterwurzacher2025-04-05T09:31:14+00:00urn:sha1:c8055829c311ecaf532fd171f3a5d104f873272d
Because if we have them in git, we get this:
$ go install github.com/rfjakob/gocryptfs/v2@latest
go: downloading github.com/rfjakob/gocryptfs/v2 v2.5.2
go: github.com/rfjakob/gocryptfs/v2@latest: create zip: tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z
g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\ng": invalid char '\n'
g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\rg": invalid char '\r'
Fixes: https://github.com/rfjakob/gocryptfs/issues/904
Relates-to: https://github.com/golang/go/issues/28001
fusefrontend: fix unconditional FileGetattrer cast2025-03-26T21:50:54+00:00Jakob Unterwurzacher2025-03-26T21:50:54+00:00urn:sha1:810f074e75b4251b1520843b42c204e5a6e376d8
Essentially a port of
https://github.com/hanwen/go-fuse/commit/531a68551e40e7303e94b53fb3792e6dfb28d15a .
This fixes
panic: interface conversion: *fs.dirStreamAsFile is not fs.FileGetattrer: missing method Getattr
goroutine 20 [running]:
github.com/rfjakob/gocryptfs/v2/internal/fusefrontend.(*Node).Getattr(0x55a7ac9d9090?, {0x55a7ac85a4d8, 0xc0013401c8}, {0x55a7ac80eb40?, 0xc0013401b0}, 0xc000586938)
github.com/rfjakob/gocryptfs/v2/internal/fusefrontend/node.go:74 +0x22c
github.com/hanwen/go-fuse/v2/fs.(*rawBridge).getattr(0xc0000b6180, {0x55a7ac85a4d8, 0xc0013401c8}, 0xc0010ea160, {0x55a7ac80eb40?, 0xc0013401b0}, 0xc000586938)
github.com/hanwen/go-fuse/v2@v2.7.2/fs/bridge.go:569 +0x9b
[...]
which is a bug exposed by a go-fuse update.
Fixes https://github.com/rfjakob/gocryptfs/issues/897
test.bash, crossbuild.bash: drop old Go version kludges2025-03-19T15:49:21+00:00Jakob Unterwurzacher2025-03-19T15:49:21+00:00urn: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 changelog2025-03-19T15:43:18+00:00Jakob Unterwurzacher2025-03-19T15:43:18+00:00urn:sha1:50eb371e9051fbcaef5aeb26198a3fd6b56061dbtest.bash: catch calls to unix.Seteuid and friends2025-03-19T15:33:16+00:00Jakob Unterwurzacher2025-03-19T15:33:16+00:00urn:sha1:34be08a1aa2b00784719d614f0f84f7f02bae2f1
https://github.com/rfjakob/gocryptfs/issues/893
github ci: clean up Go versions2025-03-11T22:25:32+00:00Jakob Unterwurzacher2025-03-11T22:25:32+00:00urn: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.conf2025-03-11T22:25:04+00:00Jakob Unterwurzacher2025-03-11T22:12:22+00:00urn: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.02025-03-01T19:54:10+00:00Jakob Unterwurzacher2025-03-01T19:54:10+00:00urn: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/sys2025-02-26T21:01:13+00:00Jakob Unterwurzacher2025-02-26T21:00:03+00:00urn: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