gocryptfs
gocryptfs copied to clipboard
Encrypted overlay filesystem written in Go
This issue is currently blocked by https://github.com/rfjakob/gocryptfs/issues/351. Once we fix that, we get: ``` --- FAIL: Test0100Dir (0.00s) correctness_test.go:243: open /var/folders/6x/tlqzyq0j38j9xw6qkl8p3jcm0000gq/T/gocryptfs-tp/025916131/c/Test0100Dir/hello: permission denied FAIL FAIL github.com/rfjakob/gocryptfs/tests/reverse 3.857s ``` This test...
This issue already exists for quite some time, but I don't think there is a bug report for it yet. I was initially hoping to fix it together with #158,...
Does gocryptfs do file locking through the fuse layer? So if a mounted & decrypted file gets a lock by a process using it, will the underlying encrypted source file...
On macOS, the xattr tests still cause a couple of test failures: ``` DecryptBlock: Block is too short: 3 bytes DecryptBlock: Block is too short: 2 bytes GetXAttr: Block is...
The current implementation of `openWriteOnlyFile` can lead to different race-conditions: * Since `openWriteOnlyLock` is only used for opening files, stat-ing a file at the wrong time might reveal the temporary...
It sounds like 1.5+ should have xattr support, referring to #217. When I `chattr +i` a file, I get: `chattr: Function not implemented while reading flags on (name of file)`...
With go now embedding build versions into the binary, this could be used if built from: `go install github.com/rfjakob/gocryptfs/v2@latest` Here is an example dump of what is present in each...
Finally! Symlink-safety without the overhead: Linux kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.19&id=fddb5d430ad9fa91b49b1d34d0202ffe2fa0e179 Merged in v5.6: $ git describe --contains fddb5d430ad9fa91b49b1d34d0202ffe2fa0e179 v5.6-rc1~133^2~2 LWN background article: https://lwn.net/Articles/796868/
installing with `go install github.com/rfjakob/gocryptfs/v2@latest` will not recognize the latest release "v2.3", even if explicitly requested by tag. Right now it fetches "v2.2.1" which is in the format it recognizes....
Ran `go get -u github.com/hanwen/go-fuse/v2@master` to get this diff As pointed out in https://github.com/rfjakob/gocryptfs/issues/595#issuecomment-1222271612, go-fuse was updated with a patch to allow `-reverse` mode on macOS!