Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2026-02-02T18:46:40+00:00 2026-02-02T18:46:40+00:00 Jakob Unterwurzacher 2026-02-02T18:46:40+00:00 urn:sha1:b239d51b65947a5dbb61e7e81ede9ecd347a2a2f 2026-01-29T20:02:52+00:00 Jakob Unterwurzacher 2026-01-29T20:02:52+00:00 urn:sha1:5ac1a51acdcc8626d536e324b1e03e2b8554ba50 2026-01-24T19:12:18+00:00 rfjakob 2026-01-24T19:12:18+00:00 urn:sha1:5185e92ec80a9998ae00cb799dfdfbb93247dfaf Summary: Store as NFC, read as NFD. This commit resolves https://github.com/rfjakob/gocryptfs/issues/850 by addressing Unicode normalization mismatches on macOS between NFC (used by CLI tools) and NFD (used by GUI apps). The solution is inspired by Cryptomator's approach ( https://github.com/cryptomator/cryptomator/issues/264 ). Forward mode on MacOS now enforces NFC for storage but presents NFD as recommended by https://developer.apple.com/library/archive/qa/qa1173/_index.html and https://github.com/macfuse/macfuse/wiki/File-Names-(Unicode-Normalization-Forms) . See https://github.com/rfjakob/gocryptfs/pull/949 for more info. This commit does nothing for reverse mode as it is not clear if anything can be done. Reverse mode can not influence how the file names are stored, hence mapping normalized names back to what is actually on disk seems difficult. 2025-12-15T20:16:54+00:00 linaseu 2025-12-05T02:54:10+00:00 urn:sha1:7b1d22affe1f43ff4dab16050f7603db9d18232b 2025-07-14T19:18:03+00:00 Jakob Unterwurzacher 2025-07-14T19:18:03+00:00 urn:sha1:cd288aba1de53d15a364a4e13d83de4bacc83878 2025-06-02T19:50:25+00:00 Jakob Unterwurzacher 2025-06-02T19:50:25+00:00 urn:sha1:fb4f2deb5116075a8a38c048cd5e67b554620181 This pulls in https://github.com/aperturerobotics/jacobsa-crypto/commit/e3f78416c5c1dbdfef68c84d62a97a809a94f4dd "fix build error on loong64 (#8)" and fixes this build error on loong64: $ GOARCH=loong64 go build -tags without_openssl # github.com/aperturerobotics/jacobsa-crypto/cmac ../../go/pkg/mod/github.com/aperturerobotics/jacobsa-crypto@v1.0.2/cmac/hash.go:97:3: undefined: xorBlock 2025-04-19T21:24:01+00:00 Jakob Unterwurzacher 2025-03-26T22:35:40+00:00 urn:sha1:7309412215551052dc4dbb6c137c568ccbd02430 Done using: go get -u github.com/hanwen/go-fuse/v2@master Upgrading to master because I want https://github.com/hanwen/go-fuse/commit/216e54932a48254d949871bf07f58d48f5046ec2 and https://github.com/hanwen/go-fuse/commit/d6170d09d743644ccf6099744e5bad1d2c3e552f which are not released yet. Fixes TestSeekDir. 2025-04-19T20:51:52+00:00 Jakob Unterwurzacher 2025-03-26T22:34:21+00:00 urn:sha1:a8bb03b438e2c58565457b0cbcba9a77a316fbd2 Done using: go get -u github.com/hanwen/go-fuse/v2 As expected, this breaks TestSeekDir: gocryptfs/tests/defaults$ go test -run TestSeekDir test_helpers: warning: testParentDir "/tmp/gocryptfs-test-parent-1026" does not reside on ext4, we will miss failures caused by ino reuse --- FAIL: TestSeekDir (0.00s) main_test.go:536: 1st getdents returned 288 bytes main_test.go:542: 2nd getdents returned 0 bytes main_test.go:551: operation not supported FAIL exit status 1 FAIL github.com/rfjakob/gocryptfs/v2/tests/defaults 0.030s 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. 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