<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/tests/reverse/config_custom_test.go, branch LockSharedStorage_rebase2</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=LockSharedStorage_rebase2</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=LockSharedStorage_rebase2'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2026-07-12T18:39:59+00:00</updated>
<entry>
<title>reverse: hide custom -config file located inside CIPHERDIR</title>
<updated>2026-07-12T18:39:59+00:00</updated>
<author>
<name>maximilize</name>
</author>
<published>2026-06-25T22:23:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=3ac282047ff36affb86f260b54ff50653007fdee'/>
<id>urn:sha1:3ac282047ff36affb86f260b54ff50653007fdee</id>
<content type='text'>
In reverse mode, a custom config file passed via -config that lives inside
CIPHERDIR was presented as an ordinary encrypted file in the encrypted view,
which is useless and confusing. By default the config is mapped to a virtual
gocryptfs.conf, but ConfigCustom skips that mapping, so an in-CIPHERDIR custom
config was neither mapped nor hidden.

Plumb the config path into the reverse RootNode and treat a custom config file
located inside CIPHERDIR as excluded in isExcludedPlain, hiding it from both
readdir and lookup. Also document the -config reverse-mode behaviour in
MANPAGE.md and add a regression test.

Fixes #1009
</content>
</entry>
</feed>
