gocryptfs/tests/cli, branch v1.8.0Mirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=v1.8.02020-02-28T21:17:59+00:00Show undecryptable filenames if they match supplied glob2020-02-28T21:17:59+00:00orcas2019-09-14T16:32:54+00:00urn:sha1:9ec042f2f62bc95154d6c8b3215a2e7853f8f5c6
Resolves https://github.com/rfjakob/gocryptfs/issues/393
tests: cli: add TestSymlinkedCipherdir2020-01-25T15:54:57+00:00Jakob Unterwurzacher2020-01-25T15:54:57+00:00urn:sha1:dc21cd357258df775e67a36cbcd70fc5f83543ad
https://github.com/rfjakob/gocryptfs/issues/450
tests: filter leaked fds by prefix2019-10-06T17:37:51+00:00Jakob Unterwurzacher2019-10-06T17:04:16+00:00urn:sha1:1fb18f4a9ef2bbbc6e7c774fa064808a3952bb3f
When running
$ go test ./tests/matrix/
in isolation, it failed like this:
fd leak? before, after:
[0r=/dev/null 3w=/dev/null 5r=/proc/8078/fd (hidden:4)]
[0r=/dev/null 3w=/dev/null 5w=/tmp/go-build366655199/b001/testlog.txt 7r=/proc/8078/fd (hidden:4)]
Filter by prefix to get rid of this spurious test failure.
tests: clarify which process seems to be leaking fds2019-10-06T16:48:09+00:00Jakob Unterwurzacher2019-10-06T16:48:09+00:00urn:sha1:d361f6e35bb97ef8f060131ea5b29f922e613c49
The tests check if they leak fds themselves, but we also
check if gocryptfs leaks fds. Clarify what is what in the
error message.
tests: add TestNotIdle2019-09-08T14:16:18+00:00Jakob Unterwurzacher2019-09-08T14:16:18+00:00urn:sha1:ce13851bbfceb02da0b36e743090c5fe54469b33
Mount with idle timeout of 100ms read something every 10ms. The fs should
NOT get unmounted. Regression test for https://github.com/rfjakob/gocryptfs/issues/421
-passwd now takes a passed -scryptn flag into account2019-05-13T21:01:44+00:00Jakob Unterwurzacher2019-05-13T21:01:44+00:00urn:sha1:991adfc934d714897e3c0ad39d37fca3edf59bcb
https://github.com/rfjakob/gocryptfs/issues/400
readpassword: delete CheckTrailingGarbage2019-04-08T18:18:45+00:00Jakob Unterwurzacher2019-04-08T18:18:45+00:00urn:sha1:fe06e9f45646893dc88ebe9e657e2e991f6f5fbb
CheckTrailingGarbage was called even when "-passfile" was
used, which is stupid, and causes false positives:
https://github.com/rfjakob/gocryptfs/issues/391
(false error "Received trailing garbage after the password"
when using -passfile in .bash_profile)
Instead of trying to improve the logic to handle that case
and make everything even more complicated, delete the function.
It is unclear if actually helps in some cases, and it definitely
harms as shown by the above bug report.
Allow "nofail" for /etc/fstab use2019-03-31T12:33:02+00:00Jakob Unterwurzacher2019-03-31T12:33:02+00:00urn:sha1:8f2723b387fd3a4f575109a42d7c91059ebfe3faforward mode: create gocryptfs.diriv files with 0440 permissions2019-03-30T19:06:40+00:00Jakob Unterwurzacher2019-03-30T19:06:40+00:00urn:sha1:ec17445b996e7a2dc3b753963ea329881430e27b
Makes it easier to share an encrypted folder via a network drive.
https://github.com/rfjakob/gocryptfs/issues/387
tests: teach ListFds() to check other processes2019-01-01T19:05:38+00:00Jakob Unterwurzacher2019-01-01T18:44:41+00:00urn:sha1:887d5aa8e74e20b065b9a0c9b6e99dd05815112a