gocryptfs/tests/fsck, branch xattr_user_buffer Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2025-04-05T09:46:07+00:00 tests: fsck: generate evil files with "\r" and "\n" on the fly 2025-04-05T09:46:07+00:00 Jakob Unterwurzacher 2025-04-05T09:31:14+00:00 urn: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 filesystem 2023-09-15T20:29:07+00:00 Jakob Unterwurzacher 2023-07-21T15:23:39+00:00 urn: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 go mod: declare module version v2 2021-08-23T13:05:15+00:00 Jakob Unterwurzacher 2021-08-23T13:05:15+00:00 urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858 Our git version is v2+ for some time now, but go.mod still declared v1. Hopefully making both match makes https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work. All the import paths have been fixed like this: find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/% tests/fsck: delete obsolete script run_fsck.bash 2021-06-26T17:27:58+00:00 Jakob Unterwurzacher 2021-06-26T17:27:58+00:00 urn:sha1:49507ea869e8496b1890bea96b182ccc93923d79 Not called by anybody. v2api: fsck: use a temporary mount 2020-07-19T21:03:47+00:00 Jakob Unterwurzacher 2020-07-19T21:03:47+00:00 urn:sha1:8915785acf7e6e7908b32103406620f243093931 Directly accessing the Nodes does not work properly, as there is no way to attach a newly LOOKUPped Node to the tree. This means Path() does not work. Use an actual mount instead and walk the tree. Add CodeLingo Tenet to fix missing close file 2019-04-10T11:33:58+00:00 leilaes 2019-04-10T07:43:34+00:00 urn:sha1:cc0a603ef8a691b01fbd0f6a99e7d4e1d36608f7 fsck: handle sparse files efficiently, fix xfstests generic/285 2018-07-01T19:48:51+00:00 Jakob Unterwurzacher 2018-07-01T17:14:00+00:00 urn:sha1:2d68b06f9dab66b2a0a6c29c8d5450e2b1d43fae If we encounter a 128KB block of zeros, try to skip to the next data section by calling File.SeekData(). This fixes xfstests generic/285, which creates a 17TB sparse file, and runs fsck afterwards. Without this optimization, fsck would take ages. trezor: add skeleton for Trezor support 2018-07-01T18:56:04+00:00 Jakob Unterwurzacher 2018-06-17T13:25:09+00:00 urn:sha1:c6f6e8ec4d71475a24ebbb0e64f19ad94249efd9 readpassword.Trezor() is not implemented yet and returns a hardcoded dummy key. fsck: update testcases with binary xattrs 2018-05-10T21:26:00+00:00 Jakob Unterwurzacher 2018-05-10T21:18:16+00:00 urn:sha1:f7a6f4d46858dcd049bcf671509bdf42e5d26d09 fsck: add xattr support 2018-04-02T18:25:59+00:00 Jakob Unterwurzacher 2018-04-02T18:25:59+00:00 urn:sha1:8b443c8484f5fdcedbec2a689a7d66d2a277b26e With testcases.