Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=aegis 2025-03-12T19:43:23+00:00 2025-03-12T19:43:23+00:00 Jakob Unterwurzacher 2025-03-12T19:42:15+00:00 urn:sha1:3b728b4a01d18a3689c81d5e69c849ff93f799ae Error was: --- FAIL: TestFallocate (0.01s) fallocate_test.go:172: Expected 8192 allocated bytes, have 12288 https://github.com/rfjakob/gocryptfs/pull/900 2025-03-12T19:43:23+00:00 Frank Denis 2025-03-12T07:27:13+00:00 urn:sha1:2130e49349689ca7937a0e8338588f7fb96030c0 2025-03-12T19:43:23+00:00 Frank Denis 2025-03-11T23:54:35+00:00 urn:sha1:d5d26d75247d4fcc269cd0494cb85c7e62618c89 2025-03-12T19:43:23+00:00 Frank Denis 2025-02-25T14:03:50+00:00 urn:sha1:779a850e0fb967aac79124c7e18b14706d5f2652 AEGIS is a new family of authenticated encryption algorithms that offers stronger security, higher usage limits, and better performance than AES-GCM. This pull request adds support for a new `-aegis` command-line flag, allowing AEGIS-128X2 to be used as an alternative to AES-GCM on CPUs with AES acceleration. It also introduces the ability to use ciphers with different key sizes. More information on AEGIS is available here: - https://cfrg.github.io/draft-irtf-cfrg-aegis-aead/draft-irtf-cfrg-aegis-aead.html - https://github.com/cfrg/draft-irtf-cfrg-aegis-aead gocryptfs -speed speed on Apple M1: AES-GCM-256-OpenSSL 3718.79 MB/s AES-GCM-256-Go 5083.43 MB/s (selected in auto mode) AES-SIV-512-Go 625.20 MB/s XChaCha20-Poly1305-OpenSSL 1358.63 MB/s (selected in auto mode) XChaCha20-Poly1305-Go 832.11 MB/s Aegis128X2-Go 11818.73 MB/s gocryptfs -speed speed on AMD Zen 4: AES-GCM-256-OpenSSL 5215.86 MB/s AES-GCM-256-Go 6918.01 MB/s (selected in auto mode) AES-SIV-512-Go 449.61 MB/s XChaCha20-Poly1305-OpenSSL 2643.48 MB/s XChaCha20-Poly1305-Go 3727.46 MB/s (selected in auto mode) Aegis128X2-Go 28109.92 MB/s 2025-02-26T20:56:25+00:00 Jakob Unterwurzacher 2025-02-26T20:56:25+00:00 urn:sha1:0024b056d668290e5105527e8ff0a3b23a3a70c8 2025-02-23T21:34:56+00:00 Jakob Unterwurzacher 2025-02-23T21:29:17+00:00 urn:sha1:178f570d4076ee9be408c9eb5e50502275a180c6 Both work with golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a but break with golang.org/x/sys v0.30.0 https://github.com/rfjakob/gocryptfs/issues/893 https://github.com/rfjakob/gocryptfs/issues/892 2025-02-17T20:37:41+00:00 Jakob Unterwurzacher 2025-02-17T20:37:41+00:00 urn:sha1:3c82930d4ad22b5be2f644346018a0550dd66aa8 I will add more tests for https://github.com/rfjakob/gocryptfs/issues/893 soon, these will also use DefaultPlainDir. 2025-01-23T21:17:51+00:00 Jakob Unterwurzacher 2025-01-23T21:16:29+00:00 urn:sha1:00d4d91048fd6ae3017ced1f3937357c14e8e548 https://github.com/rfjakob/gocryptfs/issues/893 2025-01-18T13:46:14+00:00 Jakob Unterwurzacher 2025-01-18T13:46:14+00:00 urn:sha1:a0105e65cde9f4643a896770a9629da644613a8a Darwin does not have Stat_t.mtim: + go test -c -tags without_openssl -o /dev/null github.com/rfjakob/gocryptfs/v2/tests/reverse Error: tests/reverse/correctness_test.go:407:15: name_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim) Error: tests/reverse/correctness_test.go:407:37: long_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim) Error: tests/reverse/correctness_test.go:410:15: name_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim) Error: tests/reverse/correctness_test.go:410:37: long_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim) Error: tests/reverse/correctness_test.go:424:16: diriv_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim) Error: tests/reverse/correctness_test.go:424:42: workdirA_stat.Mtim undefined (type syscall.Stat_t has no field or method Mtim) Error: tests/reverse/correctness_test.go:427:16: diriv_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim) Error: tests/reverse/correctness_test.go:427:42: workdirA_stat.Ctim undefined (type syscall.Stat_t has no field or method Ctim) Switch to os.Stat. 2025-01-18T13:27:27+00:00 Jakob Unterwurzacher 2025-01-18T13:27:27+00:00 urn:sha1:38936cba4e319525875feaa5d44b85819692e056 This problem potentially causes extra disk usage for sparse files but is otherwise harmless. Skip the test for now.