diff options
| author | Jakob Unterwurzacher | 2025-04-13 11:48:22 +0200 |
|---|---|---|
| committer | Jakob Unterwurzacher | 2025-04-13 11:52:58 +0200 |
| commit | 4851c322d5ce06c559eed9e9f3cb0a5c2c72fd5e (patch) | |
| tree | d9b35dea5011e40c44c1b9096971e992c435558a /gocryptfs-xray/xray_tests/aesgcm_fs | |
| parent | 6d513c1c8f0cb15db0be005cb5b49bf538c1aca3 (diff) | |
Revert "Build with v2 extensions" / GOAMD64=v2
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
Diffstat (limited to 'gocryptfs-xray/xray_tests/aesgcm_fs')
0 files changed, 0 insertions, 0 deletions