gocryptfs - Mirror of gocryptfs source code on Github

Age	Commit message (Collapse)	Author
5 days	Do what @rfjakob asked me to do	Frank Denis

5 days	Add optional support for AEGIS encryption	Frank Denis
	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
2021-11-01	docs: names longer than 175 bytes (not 176) are stored in longnames	Jakob Unterwurzacher
	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
2021-10-21	configfile: add LongNameMax support	Jakob Unterwurzacher
	Feature flag + numeric paramater https://github.com/rfjakob/gocryptfs/issues/499
2021-08-23	configfile: add Validate() function, support FlagXChaCha20Poly1305	Jakob Unterwurzacher
	We used to do validation using lists of mandatory feature flags. With the introduction of XChaCha20Poly1305, this became too simplistic, as it uses a different IV length, hence disabling GCMIV128. Add a dedicated function, Validate(), with open-coded validation logic. The validation and creation logic also gets XChaCha20Poly1305 support, and gocryptfs -init -xchacha now writes the flag into gocryptfs.conf.
2021-08-23	Add partial XChaCha20-Poly1305 support (mount flag only)	Jakob Unterwurzacher
	Mount flag only at the moment, not saved to gocryptfs.conf. https://github.com/rfjakob/gocryptfs/issues/452
2021-08-20	-deterministic-names: accept flag on -init	Jakob Unterwurzacher
	And store it in gocryptfs.conf (=remove DirIV feature flag).
2020-09-12	Add support for FIDO2 tokens	Pavol Rusnak

2019-12-28	remove Trezor support	Pavol Rusnak

2018-07-01	trezor: add skeleton for Trezor support	Jakob Unterwurzacher
	readpassword.Trezor() is not implemented yet and returns a hardcoded dummy key.
2017-03-05	full stack: implement HKDF support	Jakob Unterwurzacher
	...but keep it disabled by default for new filesystems. We are still missing an example filesystem and CLI arguments to explicitely enable and disable it.
2017-03-05	configfile: reject the "HKDF" flag for now	Jakob Unterwurzacher
	This will be re-enabled once it is implemented.
2017-03-05	configfile: define HKDF flag	Jakob Unterwurzacher

2016-11-01	Add support for unpadded base64 filenames, "-raw64"	Jakob Unterwurzacher
	Through base64.RawURLEncoding. New command-line parameter "-raw64".
2016-10-04	lint fixes	Valient Gough

2016-09-26	reverse: switch from GCM-SIV to AES-SIVv1.1-beta1	Jakob Unterwurzacher
	GCM-SIV is not yet finalized, and the reference implemenation is painfully slow at about 2 MB/s. Switch to AES-SIV.
2016-09-25	cryptocore: add support for GCM-SIV	Jakob Unterwurzacher

2016-06-06	configfile: warn about missing feature flags	Jakob Unterwurzacher
	The plan is to drop support for the oldest filesystem versions in gocryptfs v1.0. For now, we only warn the user.
2016-06-05	configfile: use map[flagIota] for feature flags	Jakob Unterwurzacher
	This should make things saner and more extensible. It prepares the infrastructure for "required feature flags" that will be used to deprecate old gocryptfs version.