<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/internal/configfile, branch aegis</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=aegis</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=aegis'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2025-03-12T19:43:23+00:00</updated>
<entry>
<title>Do what @rfjakob asked me to do</title>
<updated>2025-03-12T19:43:23+00:00</updated>
<author>
<name>Frank Denis</name>
</author>
<published>2025-03-11T23:32:04+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=3e852eb354f99fb95b399c68d950298b33ed88ab'/>
<id>urn:sha1:3e852eb354f99fb95b399c68d950298b33ed88ab</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add optional support for AEGIS encryption</title>
<updated>2025-03-12T19:43:23+00:00</updated>
<author>
<name>Frank Denis</name>
</author>
<published>2025-02-25T14:03:50+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=779a850e0fb967aac79124c7e18b14706d5f2652'/>
<id>urn:sha1:779a850e0fb967aac79124c7e18b14706d5f2652</id>
<content type='text'>
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
</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>MANPAGE: scryptn: list how much memory is needed</title>
<updated>2023-01-08T21:17:14+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2023-01-08T21:15:39+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=88bc0aa60748405db94410c8f149e62683638f80'/>
<id>urn:sha1:88bc0aa60748405db94410c8f149e62683638f80</id>
<content type='text'>
Calculated acc. to https://words.filippo.io/the-scrypt-parameters/ ,
and add benchmarks to double-check the numbers. They match.
</content>
</entry>
<entry>
<title>docs: names longer than 175 bytes (not 176) are stored in longnames</title>
<updated>2021-11-01T13:44:32+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-11-01T13:44:32+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d530fbd400c88fa54c856d958963d77669ac9cf2'/>
<id>urn:sha1:d530fbd400c88fa54c856d958963d77669ac9cf2</id>
<content type='text'>
Quoting fusefrontend_reverse/node_helpers.go :

	// File names are padded to 16-byte multiples, encrypted and
	// base64-encoded. We can encode at most 176 bytes to stay below the 255
	// bytes limit:
	// * base64(176 bytes) = 235 bytes
	// * base64(192 bytes) = 256 bytes (over 255!)
	// But the PKCS#7 padding is at least one byte. This means we can only use
	// 175 bytes for the file name.

Noticed by @bailey27 at https://github.com/rfjakob/gocryptfs/issues/499#issuecomment-955790427
</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>configfile: add LongNameMax support</title>
<updated>2021-10-21T12:55:30+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-10-21T07:58:37+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d583bdb79e6f05bce2451a7e220e553209da4c1d'/>
<id>urn:sha1:d583bdb79e6f05bce2451a7e220e553209da4c1d</id>
<content type='text'>
Feature flag + numeric paramater

https://github.com/rfjakob/gocryptfs/issues/499
</content>
</entry>
<entry>
<title>configfile: replace broken switch/case logic with if</title>
<updated>2021-10-21T12:55:30+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-10-21T12:47:29+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a652be805e1562948aff4dc232bd1c516ff01d00'/>
<id>urn:sha1:a652be805e1562948aff4dc232bd1c516ff01d00</id>
<content type='text'>
Because switch only matches once, we could have missed invalid
cases.

Replace the switch statements with a straight if rake.
</content>
</entry>
<entry>
<title>cli: drop -forcedecode flag</title>
<updated>2021-09-10T10:14:19+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2021-09-10T10:14:19+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a'/>
<id>urn:sha1:d023cd6c95fcbc6b5056ba1f425d2ac3df4abc5a</id>
<content type='text'>
The rewritten openssl backend does not support this flag anymore,
and it was inherently dangerour. Drop it (ignored for compatibility)
</content>
</entry>
</feed>
