Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2025-12-14T10:39:31+00:00 2025-12-14T10:39:31+00:00 Jakob Unterwurzacher 2025-12-14T10:33:25+00:00 urn:sha1:4762992b706a9d1950a86248720199ae8cd5d3e5 $ go version go version go1.25.4 linux/amd64 $ go vet ./... ./init_dir.go:71:21: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf ./main.go:123:19: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf ./masterkey.go:29:20: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf ./masterkey.go:56:20: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf ./mount.go:415:20: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf internal/tlog/log.go:76:18: non-constant format string in call to (*log.Logger).Printf internal/syscallcompat/quirks.go:19:19: non-constant format string in call to (*github.com/rfjakob/gocryptfs/v2/internal/tlog.toggledLogger).Printf 2022-01-03T14:18:59+00:00 Jakob Unterwurzacher 2022-01-03T14:18:59+00:00 urn:sha1:4b251f3ce1f0a0472ed10a00aeef70c69ba03a5d This allows cleanups to happen in the caller, like removing the control socket. Fixes https://github.com/rfjakob/gocryptfs/issues/634 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/% 2020-05-17T17:31:04+00:00 Jakob Unterwurzacher 2020-05-17T17:31:04+00:00 urn:sha1:416080203b4dd79de857eaf7c7cc97d050e00a9f Each file will be read and then concatenated for the effictive password. This can be used as a kind of multi-factor authenticiton. Fixes https://github.com/rfjakob/gocryptfs/issues/288 2020-05-09T14:53:12+00:00 Jakob Unterwurzacher 2020-05-09T14:32:11+00:00 urn:sha1:ff04b1d83ab120197add2fe4d6f6d3ff7a34f1ff This was handled both in getMasterKey(). Split it apart. 2020-05-09T14:10:22+00:00 Jakob Unterwurzacher 2020-05-09T14:10:22+00:00 urn:sha1:7622c9f538d324ba4ed704ff836942af39d2b1f9 Make it clear that function does NOT parse the "-masterkey" command line argument, it just unhexes the payload. 2019-04-08T18:18:45+00:00 Jakob Unterwurzacher 2019-04-08T18:18:45+00:00 urn:sha1:fe06e9f45646893dc88ebe9e657e2e991f6f5fbb CheckTrailingGarbage was called even when "-passfile" was used, which is stupid, and causes false positives: https://github.com/rfjakob/gocryptfs/issues/391 (false error "Received trailing garbage after the password" when using -passfile in .bash_profile) Instead of trying to improve the logic to handle that case and make everything even more complicated, delete the function. It is unclear if actually helps in some cases, and it definitely harms as shown by the above bug report. 2019-03-03T12:25:30+00:00 Jakob Unterwurzacher 2019-03-03T12:25:30+00:00 urn:sha1:cf27037f20723e934320edeff7f8aa356bdca467 To support arguments containing spaces, -extpass can now be passed multiple times. https://github.com/rfjakob/gocryptfs/issues/289 2018-12-15T16:09:38+00:00 Jakob Unterwurzacher 2018-12-15T16:09:38+00:00 urn:sha1:295d432175292dbaef572093d784aab55f5c0b8f Allows better error handling, gets rid of the call to an external program, and fixes https://github.com/rfjakob/gocryptfs/issues/278 . 2018-07-01T18:56:22+00:00 Jakob Unterwurzacher 2018-06-26T18:44:10+00:00 urn:sha1:6d64dfe8f7acd8e9ca4a659d26318e442c2db85a It is no longer printed at all when mounting a filesystem, printing on -init can be disabled with -q. https://github.com/rfjakob/gocryptfs/issues/76