gocryptfs/internal/fusefrontend, branch v1.2Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.22016-11-28T22:15:24+00:00fusefrontend: preserve owner for symlinks2016-11-28T22:15:24+00:00Jakob Unterwurzacher2016-11-28T22:15:24+00:00urn:sha1:55df8acac30c382390ca59474f1732b0f1b230b8
https://github.com/rfjakob/gocryptfs/issues/64
fusefronted: preserve owner for device nodes and sockets2016-11-28T22:09:47+00:00Jakob Unterwurzacher2016-11-28T22:09:47+00:00urn:sha1:e3c5e3f1c8db31e62bbb781a238da4cf76ed1ffc
https://github.com/rfjakob/gocryptfs/issues/64
fusefrontend: use Lchown when preserving owner2016-11-28T21:46:04+00:00Jakob Unterwurzacher2016-11-28T21:46:04+00:00urn:sha1:a66440c66816c919acfaa4cd079fe2fae7043294
This prevents (unlikely) symlink race attacks
main, fusefrontend: add "-noprealloc" option2016-11-25T08:19:14+00:00Jakob Unterwurzacher2016-11-24T21:36:04+00:00urn:sha1:0f8d3318a321bf19f92e0872d741266cd0431463
Preallocation is very slow on hdds that run btrfs. Give the
user the option to disable it. This greatly speeds up small file
operations but reduces the robustness against out-of-space errors.
Also add the option to the man page.
More info: https://github.com/rfjakob/gocryptfs/issues/63
fusefrontend: coalesce 4kB writes2016-11-25T08:03:32+00:00Jakob Unterwurzacher2016-11-23T23:03:30+00:00urn:sha1:024511d9c71558be4b1169d6bb43bd18d65539e0
This improves performance on hdds running ext4, and improves
streaming write performance on hdds running btrfs. Tar extract
slows down on btrfs for some reason.
See https://github.com/rfjakob/gocryptfs/issues/63
Benchmarks:
encfs v1.9.1
============
$ ./benchmark.bash -encfs /mnt/hdd-ext4
Testing EncFS at /mnt/hdd-ext4/benchmark.bash.u0g
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 1,48354 s, 88,4 MB/s
UNTAR: 20.79
LS: 3.04
RM: 6.62
$ ./benchmark.bash -encfs /mnt/hdd-btrfs
Testing EncFS at /mnt/hdd-btrfs/benchmark.bash.h40
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 1,52552 s, 85,9 MB/s
UNTAR: 24.51
LS: 2.73
RM: 5.32
gocryptfs v1.1.1-26-g4a7f8ef
============================
$ ./benchmark.bash /mnt/hdd-ext4
Testing gocryptfs at /mnt/hdd-ext4/benchmark.bash.1KG
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 1,55782 s, 84,1 MB/s
UNTAR: 22.23
LS: 1.47
RM: 4.17
$ ./benchmark.bash /mnt/hdd-btrfs
Testing gocryptfs at /mnt/hdd-btrfs/benchmark.bash.2t8
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 6,87206 s, 19,1 MB/s
UNTAR: 69.87
LS: 1.52
RM: 5.33
gocryptfs v1.1.1-32
===================
$ ./benchmark.bash /mnt/hdd-ext4
Testing gocryptfs at /mnt/hdd-ext4/benchmark.bash.Qt3
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 1,22577 s, 107 MB/s
UNTAR: 23.46
LS: 1.46
RM: 4.67
$ ./benchmark.bash /mnt/hdd-btrfs/
Testing gocryptfs at /mnt/hdd-btrfs//benchmark.bash.XVk
WRITE: 131072000 bytes (131 MB, 125 MiB) copied, 3,68735 s, 35,5 MB/s
UNTAR: 116.87
LS: 1.84
RM: 6.34
Fix golint warnings, add helper script2016-11-17T22:40:03+00:00Jakob Unterwurzacher2016-11-17T22:40:03+00:00urn:sha1:6f475da116edb7a86a809a25b6b47c70805ba219fusefrontend: get the file ID from the open files table2016-11-17T21:29:45+00:00Jakob Unterwurzacher2016-11-17T21:29:45+00:00urn:sha1:0489d08ae21107990d0efd0685443293aa26b35f
This fixes the problem that a truncate can reset the file
ID without the other open FDs noticing it.
fusefrontend: upgrade wlockMap to use device AND inode number2016-11-17T19:32:19+00:00Jakob Unterwurzacher2016-11-17T19:32:19+00:00urn:sha1:e04dc050126edcf7440ea5412bc74c6ad8b42e95
If there are multiple filesystems backing the gocryptfs filesystems
inode numbers are not guaranteed to be unique.
ctlsock: implement EncryptPath for reverse mode, add tests2016-11-10T22:32:51+00:00Jakob Unterwurzacher2016-11-10T22:32:51+00:00urn:sha1:c03fc46a5150715bf6aee20ce4b89d9704141220ctlsock: add initial limited implementation2016-11-09T23:27:08+00:00Jakob Unterwurzacher2016-11-09T23:27:08+00:00urn:sha1:75ebb28a625bc16d145f5acd9e0cc1d305716afe
At the moment, in forward mode you can only encrypt paths
and in reverse mode you can only decrypt paths.