gocryptfs/cli_args.go, branch xattr_user_buffer Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2026-01-18T18:48:51+00:00 added -noxattr flag which ignores all xattr operations (#987) 2026-01-18T18:48:51+00:00 Jarek Kowalski 2026-01-18T18:48:51+00:00 urn:sha1:6013d56f0c09100190107613ce8c5c4c929216dd * added -noxattr flag which ignores all xattr operations 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: mount: add -context option 2025-04-19T17:42:28+00:00 Jakob Unterwurzacher 2025-04-19T17:39:10+00:00 urn:sha1:6918a4413decccd2f535e66d12b2e3dee10a74a8 Set the SELinux context. See mount(8) for details. Add option to set FIDO2 verificatoin option 2024-04-19T20:36:55+00:00 invis-z 2023-11-21T18:12:01+00:00 urn:sha1:4b6b9553c4a2e14fd809754f6bf187957ff3cdfd Add an option to specify user verification options for `fido2-assert -t` Options will be saved to config file Provide same functionality to #705 with simpler implementation Resolve #702 init_dir: use masterkey arg 2024-03-13T09:42:53+00:00 Pablo Mazzini 2024-03-09T15:11:24+00:00 urn:sha1:8ced867c4f2a26e00e32d7703fe13aa47d9df923 cli: don't split multiple-strings flags on comma 2023-05-03T19:14:53+00:00 Jakob Unterwurzacher 2023-05-03T19:14:53+00:00 urn:sha1:aa1d8a0f90a1046b89dfdd9e58fb1407c76ff27e Looks like I used StringSliceVar (which splits on comma) where I should have always used StringArrayVar (which does not). Bug report contains this example of misbehavoir: #gocryptfs -extpass 'echo abc,123' -init testdir Reading password from extpass program "echo abc", arguments: ["123"] extpass cmd start failed: exec: "echo abc": executable file not found in $PATH Fixes https://github.com/rfjakob/gocryptfs/issues/730 Fix typos 2022-06-26T08:59:06+00:00 Yuta Hayashibe 2022-05-04T09:06:20+00:00 urn:sha1:e9ecff7f07aeb1efe0edec7b4b050ce3c0ef75f8 MANPAGE: -extpass: document dash duplication bug 2021-12-04T11:34:29+00:00 Jakob Unterwurzacher 2021-12-04T11:34:29+00:00 urn:sha1:8722b894a6fb86945b96e5c3b2cc778853e21d17 Closes https://github.com/rfjakob/gocryptfs/issues/621 docs: names longer than 175 bytes (not 176) are stored in longnames 2021-11-01T13:44:32+00:00 Jakob Unterwurzacher 2021-11-01T13:44:32+00:00 urn:sha1:d530fbd400c88fa54c856d958963d77669ac9cf2 Quoting fusefrontend_reverse/node_helpers.go : // File names are padded to 16-byte multiples, encrypted and // base64-encoded. We can encode at most 176 bytes to stay below the 255 // bytes limit: // * base64(176 bytes) = 235 bytes // * base64(192 bytes) = 256 bytes (over 255!) // But the PKCS#7 padding is at least one byte. This means we can only use // 175 bytes for the file name. Noticed by @bailey27 at https://github.com/rfjakob/gocryptfs/issues/499#issuecomment-955790427 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