<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs, branch v2.5.4</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.4</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.5.4'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2025-04-13T09:58:31+00:00</updated>
<entry>
<title>README: update changelog</title>
<updated>2025-04-13T09:58:31+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-13T09:58:31+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=b6ada0247a6967cf7dac0a94af31cd1cdc89dd41'/>
<id>urn:sha1:b6ada0247a6967cf7dac0a94af31cd1cdc89dd41</id>
<content type='text'>
</content>
</entry>
<entry>
<title>stress_tests/pingpong.bash: better comment</title>
<updated>2025-04-13T09:58:14+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-13T09:58:14+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=24a2ad252034d3b8049f90e7147de86d1d17d7c1'/>
<id>urn:sha1:24a2ad252034d3b8049f90e7147de86d1d17d7c1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "Build with v2 extensions" / GOAMD64=v2</title>
<updated>2025-04-13T09:52:58+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-13T09:48:22+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4851c322d5ce06c559eed9e9f3cb0a5c2c72fd5e'/>
<id>urn:sha1:4851c322d5ce06c559eed9e9f3cb0a5c2c72fd5e</id>
<content type='text'>
As seen in https://github.com/rfjakob/gocryptfs/issues/908,
there are users still running x86-64-v1 cpus. They get

	This program can only be run on AMD64 processors
	with v2 microarchitecture support.

and cannot read their encrypted files.

Build for AMD64v1 again an accept the XChaCha20 performance hit for
for some cpus ( https://github.com/golang/go/issues/67240 ).

This reverts commit f5007b28c366d1a9671146710975679a154f30f8.

Related:
https://github.com/rfjakob/gocryptfs/issues/828
https://github.com/rfjakob/gocryptfs/pull/833
https://github.com/apptainer/apptainer/issues/2873
https://github.com/golang/go/issues/67240
</content>
</entry>
<entry>
<title>stress_tests: fsstress-gocryptfs.bash: don't try to recompile</title>
<updated>2025-04-07T19:37:18+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-07T19:37:18+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=6d513c1c8f0cb15db0be005cb5b49bf538c1aca3'/>
<id>urn:sha1:6d513c1c8f0cb15db0be005cb5b49bf538c1aca3</id>
<content type='text'>
The days of GOPATH are over. Also, use the fsstress path
that "sudo make install" in xfstests uses per default.
</content>
</entry>
<entry>
<title>stress_tests/parallel_cp.sh: note that problem is fixed</title>
<updated>2025-04-07T19:37:03+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-07T19:27:49+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=0459e6ad1fbec7c9ae664f266916e519f095c08c'/>
<id>urn:sha1:0459e6ad1fbec7c9ae664f266916e519f095c08c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>syscallcompat: fix build contraints on thread_credentials_linux_368_arm.go</title>
<updated>2025-04-06T09:14:03+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-06T09:14:03+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=27abe23de847eff630f6768e7296cf3e6a6322b4'/>
<id>urn:sha1:27abe23de847eff630f6768e7296cf3e6a6322b4</id>
<content type='text'>
This file was only compiled for arm because
(  https://pkg.go.dev/cmd/go#hdr-Build_constraints ):

	If a file's
	name, after stripping the extension and a possible _test suffix,
	matches any of the following patterns:

	*_GOOS
	*_GOARCH
	*_GOOS_GOARCH

	(example: source_windows_amd64.go) where GOOS and GOARCH
	represent any known operating system and architecture values
	respectively, then the file is considered to have an implicit
	build constraint requiring those terms (in addition to any
	explicit constraints in the file).

Error was:

	+ GOOS=linux
	+ GOARCH=386
	+ build
	+ go build -tags without_openssl -o /dev/null
	# github.com/rfjakob/gocryptfs/v2/internal/syscallcompat
	Error: internal/syscallcompat/asuser_linux.go:41:8: undefined: Setregid
	Error: internal/syscallcompat/asuser_linux.go:47:8: undefined: Setreuid
	Error: internal/syscallcompat/thread_credentials_linux.go:29:10: undefined: setgroups
	Error: internal/syscallcompat/thread_credentials_linux.go:36:9: undefined: setgroups
	Error: internal/syscallcompat/thread_credentials_linux.go:49:9: undefined: Setregid
	Error: internal/syscallcompat/thread_credentials_linux.go:57:9: undefined: Setreuid

Rename the file to fix the problem. And add a comment about why this file exists.

Fixes https://github.com/rfjakob/gocryptfs/issues/907
</content>
</entry>
<entry>
<title>crossbuild.sh: also build on intel 32 bit (386)</title>
<updated>2025-04-06T08:59:23+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-06T08:58:31+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4551e4f8edc13aeb95f1fa372ce3bd8a0e9cba4b'/>
<id>urn:sha1:4551e4f8edc13aeb95f1fa372ce3bd8a0e9cba4b</id>
<content type='text'>
https://github.com/rfjakob/gocryptfs/issues/907
</content>
</entry>
<entry>
<title>crossbuild.sh: update broken GoArm link</title>
<updated>2025-04-06T08:59:19+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-06T08:54:41+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=0cf67b6aa9398447d1d97e0e4db22cce5135aa67'/>
<id>urn:sha1:0cf67b6aa9398447d1d97e0e4db22cce5135aa67</id>
<content type='text'>
The old link says:

&gt; The Go wiki on GitHub has moved to go.dev (#61940).
&gt;
&gt; Try https://go.dev/wiki/GoArm
</content>
</entry>
<entry>
<title>Update changelog</title>
<updated>2025-04-05T10:24:50+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-05T10:24:50+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=31f17432bfdf8bd9ca93f7a18b494d13d019d862'/>
<id>urn:sha1:31f17432bfdf8bd9ca93f7a18b494d13d019d862</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tests: fsck: generate evil files with "\r" and "\n" on the fly</title>
<updated>2025-04-05T09:46:07+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2025-04-05T09:31:14+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=c8055829c311ecaf532fd171f3a5d104f873272d'/>
<id>urn:sha1:c8055829c311ecaf532fd171f3a5d104f873272d</id>
<content type='text'>
Because if we have them in git, we get this:

	$ go install github.com/rfjakob/gocryptfs/v2@latest
	go: downloading github.com/rfjakob/gocryptfs/v2 v2.5.2
	go: github.com/rfjakob/gocryptfs/v2@latest: create zip: tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z
	g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\ng": invalid char '\n'
	g: malformed file path "tests/fsck/malleable_base64/27AG8t-XZH7G9ou2OSD_z\rg": invalid char '\r'

Fixes: https://github.com/rfjakob/gocryptfs/issues/904
Relates-to: https://github.com/golang/go/issues/28001
</content>
</entry>
</feed>
