<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/init_dir.go, branch xattr_user_buffer</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2025-12-14T10:39:31+00:00</updated>
<entry>
<title>Fix go vet 1.25.4 "non-constant format string" issues</title>
<updated>2025-12-14T10:39:31+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-12-14T10:33:25+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4762992b706a9d1950a86248720199ae8cd5d3e5'/>
<id>urn:sha1:4762992b706a9d1950a86248720199ae8cd5d3e5</id>
<content type='text'>
$ 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
</content>
</entry>
<entry>
<title>Fix a bunch of staticcheck errors</title>
<updated>2025-07-07T17:59:35+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-07-07T17:54:48+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8f5df19b353e02ffba842fd1b15ccf93da7ee3b4'/>
<id>urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4</id>
<content type='text'>
Tool-assisted.
</content>
</entry>
<entry>
<title>stupidgcm: detect AES-GCM acceleration like crypto/tls</title>
<updated>2024-06-06T08:07:08+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2024-06-06T08:07:08+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=f06f27e7bc098e334024c365004f9303e79997d9'/>
<id>urn:sha1:f06f27e7bc098e334024c365004f9303e79997d9</id>
<content type='text'>
Instead of just looking for AES, also look for PCLMULQDQ,
like crypto/tls does.

Fixes: https://github.com/rfjakob/gocryptfs/issues/822
</content>
</entry>
<entry>
<title>Add option to set FIDO2 verificatoin option</title>
<updated>2024-04-19T20:36:55+00:00</updated>
<author>
<name>invis-z</name>
</author>
<published>2023-11-21T18:12:01+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4b6b9553c4a2e14fd809754f6bf187957ff3cdfd'/>
<id>urn:sha1:4b6b9553c4a2e14fd809754f6bf187957ff3cdfd</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>init_dir: use masterkey arg</title>
<updated>2024-03-13T09:42:53+00:00</updated>
<author>
<name>Pablo Mazzini</name>
</author>
<published>2024-03-09T15:11:24+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8ced867c4f2a26e00e32d7703fe13aa47d9df923'/>
<id>urn:sha1:8ced867c4f2a26e00e32d7703fe13aa47d9df923</id>
<content type='text'>
</content>
</entry>
<entry>
<title>main: refactor BuildInfo code</title>
<updated>2022-12-29T13:43:48+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2022-12-29T13:43:09+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=99cdaa0b69e884128e8f673f96bd4d3e32743d80'/>
<id>urn:sha1:99cdaa0b69e884128e8f673f96bd4d3e32743d80</id>
<content type='text'>
Simplify and move it into a new file version.go.
</content>
</entry>
<entry>
<title>Use existing build information for version if not embedded with build script</title>
<updated>2022-12-29T13:42:13+00:00</updated>
<author>
<name>Daniel Theophanes</name>
</author>
<published>2022-12-28T15:38:09+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=439dea1b198a9edd384e3b9763a9c5672ce62b67'/>
<id>urn:sha1:439dea1b198a9edd384e3b9763a9c5672ce62b67</id>
<content type='text'>
Go1.12 introduced BuildInfo which embeds build information. It does
not embed build date to facilitate reproducable builds by default.
If build information is embedded from build script, use the information
provided by the Go build system.
</content>
</entry>
<entry>
<title>readpassword: bubble up errors instead of exiting the process</title>
<updated>2022-01-03T14:18:59+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2022-01-03T14:18:59+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4b251f3ce1f0a0472ed10a00aeef70c69ba03a5d'/>
<id>urn:sha1:4b251f3ce1f0a0472ed10a00aeef70c69ba03a5d</id>
<content type='text'>
This allows cleanups to happen in the caller, like removing
the control socket.

Fixes https://github.com/rfjakob/gocryptfs/issues/634
</content>
</entry>
<entry>
<title>cli: add -longnamemax</title>
<updated>2021-10-21T13:58:19+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-10-21T13:58:19+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d14c9340d6fb473e9837e91db8b6e869c37ad8e5'/>
<id>urn:sha1:d14c9340d6fb473e9837e91db8b6e869c37ad8e5</id>
<content type='text'>
Fixes https://github.com/rfjakob/gocryptfs/issues/499
</content>
</entry>
<entry>
<title>-init: suggest xchacha if we don't have AES accel</title>
<updated>2021-09-28T16:09:31+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-09-28T15:43:36+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=e8e35982845f36e714b915350eaf6855487aa0e8'/>
<id>urn:sha1:e8e35982845f36e714b915350eaf6855487aa0e8</id>
<content type='text'>
Example on Raspberry Pi 4:

$ ./gocryptfs/gocryptfs -init $(mktemp -d)
Notice: Your CPU does not have AES acceleration. Consider using -xchacha for better performance.
Choose a password for protecting your files.
Password:

https://github.com/rfjakob/gocryptfs/issues/607
</content>
</entry>
</feed>
