gocryptfs/tests/fsck/malleable_base64, branch xattr_user_bufferMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer2025-04-05T09:46:07+00:00tests: 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
tests/fsck: add malleable_base64 test filesystem2023-09-15T20:29:07+00:00Jakob Unterwurzacher2023-07-21T15:23:39+00:00urn:sha1:30c0fbd98ab3606956ea4cf9b99825b942ebe94c
This filesystem contains filenames with non-canonical base64
encodings of the same name "foo", leading to this mess:
$ ls mnt/
foo foo foo foo