gocryptfs/internal/configfile, branch master Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=master 2026-03-08T20:36:42+00:00 make format 2026-03-08T20:36:42+00:00 Jakob Unterwurzacher 2026-03-08T20:36:42+00:00 urn:sha1:a456b934b62ba91feea973783f67a7df26d23224 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. 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 MANPAGE: scryptn: list how much memory is needed 2023-01-08T21:17:14+00:00 Jakob Unterwurzacher 2023-01-08T21:15:39+00:00 urn:sha1:88bc0aa60748405db94410c8f149e62683638f80 Calculated acc. to https://words.filippo.io/the-scrypt-parameters/ , and add benchmarks to double-check the numbers. They match. 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 configfile: add LongNameMax support 2021-10-21T12:55:30+00:00 Jakob Unterwurzacher 2021-10-21T07:58:37+00:00 urn:sha1:d583bdb79e6f05bce2451a7e220e553209da4c1d Feature flag + numeric paramater 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. cli: drop -forcedecode flag 2021-09-10T10:14:19+00:00 Jakob Unterwurzacher 2021-09-10T10:14:19+00:00 urn:sha1:d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a The rewritten openssl backend does not support this flag anymore, and it was inherently dangerour. Drop it (ignored for compatibility)