gocryptfs/internal/configfile/validate.go, branch xattr_user_buffer Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2025-07-07T17:59:35+00:00 Fix a bunch of staticcheck errors 2025-07-07T17:59:35+00:00 Jakob Unterwurzacher 2025-07-07T17:54:48+00:00 urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4 Tool-assisted. cli: add -longnamemax 2021-10-21T13:58:19+00:00 Jakob Unterwurzacher 2021-10-21T13:58:19+00:00 urn:sha1:d14c9340d6fb473e9837e91db8b6e869c37ad8e5 Fixes https://github.com/rfjakob/gocryptfs/issues/499 configfile: replace broken switch/case logic with if 2021-10-21T12:55:30+00:00 Jakob Unterwurzacher 2021-10-21T12:47:29+00:00 urn:sha1:a652be805e1562948aff4dc232bd1c516ff01d00 Because switch only matches once, we could have missed invalid cases. Replace the switch statements with a straight if rake. configfile: add Validate() function, support FlagXChaCha20Poly1305 2021-08-23T14:00:41+00:00 Jakob Unterwurzacher 2021-08-21T19:43:26+00:00 urn:sha1:97d8340bd81ddd60baac598d3e25ebfb4decb50c We used to do validation using lists of mandatory feature flags. With the introduction of XChaCha20Poly1305, this became too simplistic, as it uses a different IV length, hence disabling GCMIV128. Add a dedicated function, Validate(), with open-coded validation logic. The validation and creation logic also gets XChaCha20Poly1305 support, and gocryptfs -init -xchacha now writes the flag into gocryptfs.conf.