gocryptfs, branch v2.2.0-beta2 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.2.0-beta2 2021-09-15T14:09:26+00:00 README: release will be called v2.2.0 instead of v2.2 2021-09-15T14:09:26+00:00 Jakob Unterwurzacher 2021-09-15T14:09:26+00:00 urn:sha1:53d51acd2b321ac50638998f81d268ea58236410 pkg.go.dev really wants that we want to comply with https://golang.org/doc/modules/version-numbers . Trying v2.2-beta1 as in https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2@v2.2-beta1 said "v2.2-beta1 is not a valid semantic version.". -speed: print cpu model 2021-09-14T16:58:22+00:00 Jakob Unterwurzacher 2021-09-14T16:47:41+00:00 urn:sha1:2d0ba24ecab375f276f024bc014faad9a7ef169c When somebody posts "gocryptfs -speed" results, they are most helpful together with the CPU model. Add the cpu model to the output. Example: $ ./gocryptfs -speed gocryptfs v2.2.0-beta1-5-g52b0444-dirty; go-fuse v2.1.1-0.20210825171523-3ab5d95a30ae; 2021-09-14 go1.17.1 linux/amd64 cpu: Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz; with AES acceleration AES-GCM-256-OpenSSL 862.79 MB/s AES-GCM-256-Go 997.71 MB/s (selected in auto mode) AES-SIV-512-Go 159.58 MB/s XChaCha20-Poly1305-OpenSSL 729.65 MB/s XChaCha20-Poly1305-Go 843.97 MB/s (selected in auto mode) stupidgcm: add CpuHasAES() 2021-09-14T16:58:04+00:00 Jakob Unterwurzacher 2021-09-14T16:47:07+00:00 urn:sha1:61e37b2439f0b8a7c16458e73cb57c7428fe61f2 Makes the code clearer, and will be used in the next commit. README: update example -speed output 2021-09-14T08:18:24+00:00 Jakob Unterwurzacher 2021-09-14T08:18:24+00:00 urn:sha1:52b044498529c4abd1d2044eabd709047e1194b5 -speed: drop useless tab at end of line 2021-09-14T08:15:18+00:00 Jakob Unterwurzacher 2021-09-14T08:15:18+00:00 urn:sha1:cdbc48fe297388392d95c0757a6099d01a50347b README: highlight changes in v2.2, simplify pkg.go.dev link 2021-09-12T16:12:10+00:00 Jakob Unterwurzacher 2021-09-12T16:12:10+00:00 urn:sha1:d0cba59f6b2b8bd62c4c09b6f511d6a9f857ae3b README: update changelog 2021-09-10T15:19:51+00:00 Jakob Unterwurzacher 2021-09-10T15:19:51+00:00 urn:sha1:2a4380ac258a8cb7d68ba5b165917bb816006320 inomap: deterministically set root device 2021-09-10T15:17:16+00:00 Jakob Unterwurzacher 2021-09-10T15:17:16+00:00 urn:sha1:c9b825c58a9f996379108926754513bca03bb306 We used to have "first Translate() wins". This is not deterministic, as the LOOKUP for the root directory does not seem to reach us, so the first user LOOKUP would win, which may be on a mountpoint. README: update changelog for v2.2-beta1 2021-09-10T10:22:02+00:00 Jakob Unterwurzacher 2021-09-10T10:22:02+00:00 urn:sha1:ee561035707527dee48cecfc9466ab4921666b43 Update README & MANPAGE 2021-09-10T10:17:22+00:00 Jakob Unterwurzacher 2021-09-10T10:17:22+00:00 urn:sha1:a85e39f68288af3b9238f7caeefe6eb420b44f02