Age | Commit message (Collapse) | Author |
|
"go get -d" does not download to GOPATH/src anymore:
https://github.com/golang/go/issues/31529
Use explicit "git clone" to the current directory as suggested
in https://github.com/golang/go/issues/31529#issuecomment-484920157 .
Fixes https://github.com/rfjakob/gocryptfs/issues/553
|
|
Pass through system.posix_acl_access and system.posix_acl_default
unencrypted to fix "cp -a" problems.
"cp -a" uses "setxattr" even to set normal permissions, see
https://www.spinics.net/lists/linux-nfs/msg63986.html .
Fixes https://github.com/rfjakob/gocryptfs/issues/543
|
|
https://github.com/rfjakob/gocryptfs/issues/543
https://github.com/rfjakob/gocryptfs/issues/542
https://github.com/rfjakob/gocryptfs/issues/453
|
|
https://github.com/rfjakob/gocryptfs/issues/544
|
|
Adding support for Trezor was listed, but removal was not,
causing confusion.
Closes https://github.com/rfjakob/gocryptfs/pull/534
|
|
world-readable
Make `gocryptfs.diriv` and `gocryptfs.xxx.name` files world-readable to make encrypted backups easier
when mounting via fstab.
Having the files follow chmod/chown of their parent does not seem
to be worth the hassle. The content of the diriv files is not
secret, and both diriv and name files are protected by the
perms of the parent dir.
Fixes https://github.com/rfjakob/gocryptfs/issues/539
|
|
When a process has its working dir inside the mount,
the only way we notice is that we get EBUSY when trying
to unmount.
We used to lazy-unmount in this case, but this means
pulling the rug from under the process.
For example, bash will start throwing
cd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
messages.
Fixes https://github.com/rfjakob/gocryptfs/issues/533
|
|
|
|
|
|
This is *very* hard to find.
https://github.com/rfjakob/gocryptfs/issues/152
|
|
|
|
|
|
|
|
Fixes https://github.com/rfjakob/gocryptfs/issues/453
|
|
|
|
This was a new feature flag.
|
|
|
|
|
|
Just added a note to preinstall fuse, so the standalone
binary will work without problem.
|
|
|
|
|
|
https://github.com/rfjakob/gocryptfs/issues/400
|
|
|
|
Makes it easier to share an encrypted folder via a network drive.
https://github.com/rfjakob/gocryptfs/issues/387
|
|
|
|
https://github.com/rfjakob/gocryptfs/issues/382
|
|
|
|
To support arguments containing spaces, -extpass can now
be passed multiple times.
https://github.com/rfjakob/gocryptfs/issues/289
|
|
|
|
|
|
|
|
Found with the 'codespell' utility.
|
|
|
|
Mostly detected with the 'codespell' utility, but also includes some
manual grammar fixes.
|
|
The CPU-Benchmarks wiki page has a lot more info
than openssl-gcm.md had.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://github.com/rfjakob/gocryptfs/issues/235
|
|
|
|
|
|
|
|
10 second animation that shows what gocryptfs does.
|
|
Also update the performance numbers. I see some slowdown, reason
is not yet clear, but nothing to block the release.
|
|
OpenDir and ListXAttr skip over corrupt entries,
readFileID treats files the are too small as empty.
This improves usability in the face of corruption,
but hides the problem in a log message instead of
putting it in the return code.
Create a channel to report these corruptions to fsck
so it can report them to the user.
Also update the manpage and the changelog with the -fsck option.
Closes https://github.com/rfjakob/gocryptfs/issues/191
|
|
At the moment, only for reverse mode.
https://github.com/rfjakob/gocryptfs/issues/217
|
|
https://github.com/rfjakob/gocryptfs/issues/218
|