| Age | Commit message (Collapse) | Author |
|---|
|
Unless we are mounted with -suid, we can reject
these requests, and gain back some lost speed.
Closes https://github.com/rfjakob/gocryptfs/issues/515
|
|
|
|
As expected, we are slow. Fd caching will be implemented later.
|
|
|
|
|
|
Each file will be read and then concatenated
for the effictive password. This can be used as a
kind of multi-factor authenticiton.
Fixes https://github.com/rfjakob/gocryptfs/issues/288
|
|
|
|
Bisecting shows that the performance drop is caused by
this commit:
commit ca9e912a28b901387e1dbb85f6c531119f2d5ef2 (refs/bisect/bad)
Author: Jakob Unterwurzacher <jakobunt@gmail.com>
Date: Sat Feb 29 19:58:08 2020 +0100
fusefrontend: drop xattr user namespace restriction
|
|
|
|
Also add big signs where the cpu has changed, as the results
are not comparable when the cpu is different.
Also update encfs results.
|
|
|
|
Feedback received during the recent Go user group. If you haven't
used FUSE before, you don't know how to unmount, and it was not
described in the man page!
As for the options, there are many, and new users are intimidated
by it. State clearly that defaults are fine.
|
|
|
|
|
|
|
|
|
|
When generating man pages, pandoc marks indented code blocks with the
roff macro '.nf'. That avoids a warning from man related to the long
line about the master key.
|
|
|
|
|
|
This adds support for gitignore-like wildcards and exclude patters in
reverse mode. It (somewhat) fixes #273: no regexp support, but the
syntax should be powerful enough to satisfy most needs.
Also, since adding a lot of --exclude options can be tedious, it adds
the --exclude-from option to read patterns from a file (or files).
|
|
...not gocryptfs here.
https://github.com/rfjakob/gocryptfs/pull/380
|
|
To support arguments containing spaces, -extpass can now
be passed multiple times.
https://github.com/rfjakob/gocryptfs/issues/289
|
|
This gives users who build from the source tarball, but
do not want to install pandoc, access to the man pages.
Apperently the gocryptfs homebrew package ships without
the man pages at the moment to avoid pandoc.
Requested at
https://github.com/rfjakob/gocryptfs/issues/355
|
|
|
|
Update output and add a nice plot.
|
|
|
|
|
|
|
|
have MANPAGE-render.bash generate both gocryptfs.1 and gocryptfs-xray.1
|
|
|
|
Fixes https://github.com/rfjakob/gocryptfs/issues/299
|
|
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.
|
|
Allows better error handling, gets rid of the call to an
external program, and fixes https://github.com/rfjakob/gocryptfs/issues/278 .
|
|
|
|
|
|
|
|
Also fix "--", which was shown as just "-" in the man pager.
|
|
|
|
https://github.com/rfjakob/gocryptfs/issues/235
|
|
For large files, the overhead will be 0.78125 %.
|
|
We only had an "options" section which was
mislabeled as "description". Add a proper description text.
|
|
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
|
|
https://github.com/rfjakob/gocryptfs/issues/218
|
|
The man page is rendered on github at
https://github.com/rfjakob/gocryptfs/blob/master/Documentation/MANPAGE.md .
Improve formatting a little.
|
|
Also update the v1.4.3 release date to today.
The release was delayed one day.
|
|
|
|
Was unclear for new users - see https://github.com/rfjakob/gocryptfs/issues/194
|
