<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/build.bash, 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-04-13T09:52:58+00:00</updated>
<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>Build with v2 extensions</title>
<updated>2024-04-18T16:55:23+00:00</updated>
<author>
<name>zp</name>
</author>
<published>2024-03-17T04:24:19+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=f5007b28c366d1a9671146710975679a154f30f8'/>
<id>urn:sha1:f5007b28c366d1a9671146710975679a154f30f8</id>
<content type='text'>
Enables older CPUs (2008-2013) to take advantage of certain hardware accelerators.
Closes #828
</content>
</entry>
<entry>
<title>build.bash: also try BSD date syntax for converting SOURCE_DATE_EPOCH</title>
<updated>2021-09-28T16:17:58+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-07-29T17:42:52+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=5406284b9b02c4115d6d351214039b9825618771'/>
<id>urn:sha1:5406284b9b02c4115d6d351214039b9825618771</id>
<content type='text'>
GNU date syntax does not work on macos.

Fixes https://github.com/rfjakob/gocryptfs/issues/570
</content>
</entry>
<entry>
<title>Drop workarounds for Go 1.11 and Go 1.12</title>
<updated>2021-08-18T15:48:38+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-08-18T15:41:33+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=b2abb0484f249849a771f5810316eab72e0a29e5'/>
<id>urn:sha1:b2abb0484f249849a771f5810316eab72e0a29e5</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add contrib/atomicrename</title>
<updated>2021-06-04T20:17:13+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-06-04T20:16:41+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=3a1f009c1ad281f37a7643b32a63057dd9c2a16e'/>
<id>urn:sha1:3a1f009c1ad281f37a7643b32a63057dd9c2a16e</id>
<content type='text'>
$ ./contrib/atomicrename/atomicrename -h
atomicrename creates 100 "src" files in the current directory, renames
them in random order over a single "dst" file while reading the "dst"
file concurrently in a loop.

Progress and errors are reported as they occour in addition to a summary
printed at the end. cifs and fuse filesystems are known to fail, local
filesystems and nfs seem ok.

See https://github.com/hanwen/go-fuse/issues/398 for background info.
</content>
</entry>
<entry>
<title>Add contrib/findholes</title>
<updated>2021-05-26T11:17:56+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-05-24T12:26:20+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8bccd3b4bf18d6505723b1c5ae30de4bbaad126e'/>
<id>urn:sha1:8bccd3b4bf18d6505723b1c5ae30de4bbaad126e</id>
<content type='text'>
Utility and libs to find hole/data segments using lseek.
</content>
</entry>
<entry>
<title>build.bash: show "go mod edit -replace" in version string</title>
<updated>2020-10-03T22:12:46+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-10-03T20:47:12+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=fe340477b2471ed03510339ca51bfcc396b03040'/>
<id>urn:sha1:fe340477b2471ed03510339ca51bfcc396b03040</id>
<content type='text'>
If you do something like this,

  go mod edit -replace github.com/hanwen/go-fuse/v2=/home/jakob/go/src/github.com/hanwen/go-fuse

the version string of the resulting binary should reflect that.

Before:

  gocryptfs v1.8.0-135-g352b547-dirty.gofuse_v2api; go-fuse v2.0.4-0.20200908172753-0b6cbc515082; 2020-10-03 go1.15.2 linux/amd64

After:

  gocryptfs v1.8.0-135-g352b547-dirty.gofuse_v2api; go-fuse v2.0.4-0.20200908172753-0b6cbc515082 =&gt; /home/jakob/go/src/github.com/hanwen/go-fuse; 2020-10-03 go1.15.2 linux/amd64
</content>
</entry>
<entry>
<title>Update go-fuse import path to github.com/hanwen/go-fuse/v2</title>
<updated>2020-05-17T12:23:47+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-05-17T12:18:23+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=ec74d1d2f4217a9a337d1db9902f32ae2aecaf33'/>
<id>urn:sha1:ec74d1d2f4217a9a337d1db9902f32ae2aecaf33</id>
<content type='text'>
We need
https://github.com/hanwen/go-fuse/commit/fd7328faf9fdf75709f7ba7df7072aaf4eeb18b3
to fix a crash reported in https://github.com/rfjakob/gocryptfs/issues/430 :

  2019/10/30 17:14:16 Unknown opcode 2016
  panic: runtime error: invalid memory address or nil pointer dereference
  [signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x508d38]

This patch is only in the v2.x.x branch. Upgrade to v2, as the
old API is also supported there.

Running

  git grep hanwen/go-fuse | grep -v hanwen/go-fuse/v2

to check for forgotten references comes back clean.
</content>
</entry>
<entry>
<title>build.bash: handle missing git tags</title>
<updated>2020-04-18T15:44:51+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-04-18T15:44:51+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=1c169ac55e79acb098c858a0448b9f30a4620a98'/>
<id>urn:sha1:1c169ac55e79acb098c858a0448b9f30a4620a98</id>
<content type='text'>
The case of a git repo without any tags used to fail
with:

  fatal: No names found, cannot describe anything.

Now we continue, using "[no_tags_found]" as the
version string.
</content>
</entry>
<entry>
<title>build.bash: don't enable -buildmode=pie for static builds</title>
<updated>2020-04-18T15:09:25+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2020-04-18T14:55:41+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=5da5e9fdf2db0f3c709a6662604d768865462068'/>
<id>urn:sha1:5da5e9fdf2db0f3c709a6662604d768865462068</id>
<content type='text'>
Causes warnings:

  $ ./build-without-openssl.bash
  # github.com/rfjakob/gocryptfs
  loadinternal: cannot find runtime/cgo
  # github.com/rfjakob/gocryptfs/gocryptfs-xray
  loadinternal: cannot find runtime/cgo
  # github.com/rfjakob/gocryptfs/contrib/statfs
  loadinternal: cannot find runtime/cgo
  gocryptfs v1.7.1-48-gf6b1c68 without_openssl; go-fuse v1.0.1-0.20190319092520-161a16484456; 2020-04-18 go1.13.6 linux/amd64

https://github.com/golang/go/issues/30986
</content>
</entry>
</feed>
