gocryptfs/tests/reverse/ctlsock_test.go, branch xattr_user_bufferMirror of gocryptfs source code on Githubhttp://nuetzlich.net/cgit/gocryptfs/atom?h=xattr_user_buffer2025-07-07T17:59:35+00:00Fix a bunch of staticcheck errors2025-07-07T17:59:35+00:00Jakob Unterwurzacher2025-07-07T17:54:48+00:00urn:sha1:8f5df19b353e02ffba842fd1b15ccf93da7ee3b4
Tool-assisted.
go mod: declare module version v22021-08-23T13:05:15+00:00Jakob Unterwurzacher2021-08-23T13:05:15+00:00urn:sha1:69d88505fd7f4cb0d9e4f1918de296342fe05858
Our git version is v2+ for some time now, but go.mod
still declared v1. Hopefully making both match makes
https://pkg.go.dev/github.com/rfjakob/gocryptfs/v2 work.
All the import paths have been fixed like this:
find . -name \*.go | xargs sed -i s%github.com/rfjakob/gocryptfs/%github.com/rfjakob/gocryptfs/v2/%
ctlsock: create exported ctlsock client library2020-05-09T15:36:41+00:00Jakob Unterwurzacher2020-05-09T15:36:41+00:00urn:sha1:16221facb9066ccf03015ccfe9e7ca784b0d2099
The former interal ctlsock server package is renamed
to ctlsocksrv.
tests: add fd leak retry logic to UnmountErr, really return error2019-01-02T00:09:09+00:00Jakob Unterwurzacher2019-01-02T00:09:09+00:00urn:sha1:772afa93f98aa77959995e42564b898057c59b87
Give the gocryptfs process one extra millisecond to close
files. Allows us to drop several other sleeps.
UnmountErr now really returns an error when it detects an fd leak
instead of just printing a message.
tests: reverse: add ctlsocket cleanup delay2019-01-01T23:09:17+00:00Jakob Unterwurzacher2019-01-01T21:54:41+00:00urn:sha1:035b3367b7a447adc5e4c1ed96706f911c08c9f8fsck: clean up log output2018-04-02T16:32:30+00:00Jakob Unterwurzacher2018-04-02T16:32:30+00:00urn:sha1:b6c8960b01f9e5366814b0dada57a0b1e6a031d9
Make sure we get only 1 warning output per
problem.
Also, add new corruption types to broken_fs_v1.4.
fusefrontend_reverse: Do not mix up cache information for different directories2017-11-25T15:20:48+00:00Sebastian Lackner2017-11-23T23:44:06+00:00urn:sha1:90687215a42b2e074f3b5a85cf344ca998fa34ac
Fixes https://github.com/rfjakob/gocryptfs/issues/168
Steps to reproduce the problem:
* Create a regular reverse mount point
* Create files with the same very long name in multiple directories - so far
everything works as expected, and it will appear with a different name each
time, for example, gocryptfs.longname.A in directory A and
gocryptfs.longname.B in directory B
* Try to access a path with A/gocryptfs.longname.B or B/gocryptfs.longname.A -
this should fail, but it actually works.
The problem is that the longname cache only uses the path as key and not the
dir or divIV. Assume an attacker can directly interact with a reverse mount and
knows the relation longname path -> unencoded path in one directory, it allows
to test if the same unencoded filename appears in any other directory.
tests: reverse: don't run tests that ignore "-plaintextnames" twice2017-03-07T19:53:58+00:00Jakob Unterwurzacher2017-03-07T19:53:58+00:00urn:sha1:a80d798c2deab44e2abc37eeae59546f0d7eec40
TestMain() runs all tests twice, once with plaintextnames=true and once
with false. Several tests mount their own filesystem and ignore the
plaintextnames variable. It makes no sense to run them twice, so
skip execution when plaintextnames is set.
ctlsock: prevent panic on invalid decrypt request2016-11-10T22:51:47+00:00Jakob Unterwurzacher2016-11-10T22:51:47+00:00urn:sha1:d8fb28a1c38cda0b013c617404ad4a768effb704ctlsock: implement EncryptPath for reverse mode, add tests2016-11-10T22:32:51+00:00Jakob Unterwurzacher2016-11-10T22:32:51+00:00urn:sha1:c03fc46a5150715bf6aee20ce4b89d9704141220