Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer 2016-02-06T18:22:35+00:00 2016-02-06T18:22:35+00:00 Jakob Unterwurzacher 2016-02-06T18:20:54+00:00 urn:sha1:2b8cbd944149afe51fadddbd67ee4499d1d86250 "git status" for reference: deleted: cryptfs/cryptfs.go deleted: cryptfs/names_core.go modified: integration_tests/cli_test.go modified: integration_tests/helpers.go renamed: cryptfs/config_file.go -> internal/configfile/config_file.go renamed: cryptfs/config_test.go -> internal/configfile/config_test.go renamed: cryptfs/config_test/.gitignore -> internal/configfile/config_test/.gitignore renamed: cryptfs/config_test/PlaintextNames.conf -> internal/configfile/config_test/PlaintextNames.conf renamed: cryptfs/config_test/StrangeFeature.conf -> internal/configfile/config_test/StrangeFeature.conf renamed: cryptfs/config_test/v1.conf -> internal/configfile/config_test/v1.conf renamed: cryptfs/config_test/v2.conf -> internal/configfile/config_test/v2.conf renamed: cryptfs/kdf.go -> internal/configfile/kdf.go renamed: cryptfs/kdf_test.go -> internal/configfile/kdf_test.go renamed: cryptfs/cryptfs_content.go -> internal/contentenc/content.go new file: internal/contentenc/content_api.go renamed: cryptfs/content_test.go -> internal/contentenc/content_test.go renamed: cryptfs/file_header.go -> internal/contentenc/file_header.go renamed: cryptfs/intrablock.go -> internal/contentenc/intrablock.go renamed: cryptfs/address_translation.go -> internal/contentenc/offsets.go new file: internal/cryptocore/crypto_api.go renamed: cryptfs/gcm_go1.4.go -> internal/cryptocore/gcm_go1.4.go renamed: cryptfs/gcm_go1.5.go -> internal/cryptocore/gcm_go1.5.go renamed: cryptfs/nonce.go -> internal/cryptocore/nonce.go renamed: cryptfs/openssl_aead.go -> internal/cryptocore/openssl_aead.go renamed: cryptfs/openssl_benchmark.bash -> internal/cryptocore/openssl_benchmark.bash renamed: cryptfs/openssl_test.go -> internal/cryptocore/openssl_test.go new file: internal/nametransform/name_api.go new file: internal/nametransform/names_core.go renamed: cryptfs/names_diriv.go -> internal/nametransform/names_diriv.go renamed: cryptfs/names_noiv.go -> internal/nametransform/names_noiv.go renamed: cryptfs/names_test.go -> internal/nametransform/names_test.go new file: internal/nametransform/pad16.go renamed: cryptfs/log.go -> internal/toggledlog/log.go renamed: cryptfs/log_go1.4.go -> internal/toggledlog/log_go1.4.go renamed: cryptfs/log_go1.5.go -> internal/toggledlog/log_go1.5.go modified: main.go modified: masterkey.go modified: pathfs_frontend/file.go modified: pathfs_frontend/file_holes.go modified: pathfs_frontend/fs.go modified: pathfs_frontend/fs_dir.go modified: pathfs_frontend/names.go modified: test.bash 2015-12-19T14:02:29+00:00 Jakob Unterwurzacher 2015-12-19T13:41:39+00:00 urn:sha1:1caa9258685fa5fad8935d3bfcd0eac7d7f84f1e This pushes back the birthday bound for collisions to make it virtually irrelevant. 2015-12-08T12:22:57+00:00 Jakob Unterwurzacher 2015-12-08T12:22:57+00:00 urn:sha1:f4ae0304aff2f721ebe6088aa4f4c83f872f1ee9 Results of cryptfs/openssl_benchmark.bash : Before: BenchmarkEnc_OpenSSL_4k_AES256_nonce96-2 50000 31802 ns/op 127.28 MB/s BenchmarkEnc_OpenSSL_4k_AES256_nonce128-2 50000 32110 ns/op 126.06 MB/s After: BenchmarkEnc_OpenSSL_4k_AES256_nonce96-2 50000 28612 ns/op 141.47 MB/s BenchmarkEnc_OpenSSL_4k_AES256_nonce128-2 50000 28613 ns/op 141.47 MB/s 2015-10-06T20:27:37+00:00 Jakob Unterwurzacher 2015-10-06T20:27:37+00:00 urn:sha1:a3d286069f989dd16c6f91930a0df9fedfa2dd64 2015-10-06T18:51:35+00:00 Jakob Unterwurzacher 2015-10-06T18:51:35+00:00 urn:sha1:5c6df490678e7dc1aa7a09425d2fdf14fb13f7be AES-256 seems to be becoming the industry standard. While AES-128 is good enough for tens of years to come, let's follow suit and be extra safe. 2015-10-04T21:58:22+00:00 Jakob Unterwurzacher 2015-10-04T21:55:58+00:00 urn:sha1:53ecebc71ec132fc8e5fab486c63e13c0925d142 2015-10-04T12:49:47+00:00 Jakob Unterwurzacher 2015-10-04T12:36:20+00:00 urn:sha1:89fef80d32708874c95742db0a7b593bcfd3b31d 2015-09-06T08:42:34+00:00 Jakob Unterwurzacher 2015-09-06T08:38:43+00:00 urn:sha1:58d1e24b7c4eb69376dd0ec230c42ea9aeb70f2d This brings streaming read performance from 30MB/s to 81MB/s (similar improvement for writes)