<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/tests/matrix, branch v1.4.4</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4.4</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4.4'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2018-03-06T20:28:09+00:00</updated>
<entry>
<title>tests: drop "-z" from fusermount to catch forgotten fds</title>
<updated>2018-03-06T20:28:09+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-06T20:22:01+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=98f735ff6e05ef71753f1c2fa60c30b195b02d3d'/>
<id>urn:sha1:98f735ff6e05ef71753f1c2fa60c30b195b02d3d</id>
<content type='text'>
macos does not have lazy unmount, so let's not use it
on linux either.
If the unmount fails, run "lsof" to find the open file.

Also fix the first bug we found this way.
</content>
</entry>
<entry>
<title>tests: matrix_test: skip cases when without_openssl is set</title>
<updated>2018-03-05T22:11:27+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-05T22:11:27+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=1789a5ea5b5f358eee18f869fb06ca25b3fd7a21'/>
<id>urn:sha1:1789a5ea5b5f358eee18f869fb06ca25b3fd7a21</id>
<content type='text'>
Fixes test-without-openssl.bash.
</content>
</entry>
<entry>
<title>macos: doTestUtimesNano: skip UTIME_OMIT and nanoseconds testcases</title>
<updated>2018-03-05T21:52:05+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-05T21:45:45+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=870779ab1ddd38d21b14460822704b6cf8dc4de6'/>
<id>urn:sha1:870779ab1ddd38d21b14460822704b6cf8dc4de6</id>
<content type='text'>
Not supported on macos.

Beef up the first test case a little by using different second
values.
</content>
</entry>
<entry>
<title>tests: TestUtimesNano: replace ugly compareUtimes wrapper</title>
<updated>2018-03-05T21:22:35+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-05T21:22:35+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=426b9536df01ba1229f506842d3948953eefcfc7'/>
<id>urn:sha1:426b9536df01ba1229f506842d3948953eefcfc7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>tests: fix a few fd leaks</title>
<updated>2018-03-05T21:00:59+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-05T20:56:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=3064d72b9774029ab89daea8a7fccfe181c3cae0'/>
<id>urn:sha1:3064d72b9774029ab89daea8a7fccfe181c3cae0</id>
<content type='text'>
We relied on the finalizer to close a few fds.
For some reason, this did not cause problems on Linux,
but on MacOS, it causes unmount failures:

umount(/private/tmp/gocryptfs-test-parent/194654785/default-plain): Resource busy -- try 'diskutil unmount'
</content>
</entry>
<entry>
<title>macos: skip TestUtimesNanoSymlink early</title>
<updated>2018-03-05T20:36:16+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-03-05T20:32:07+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=aa65091bb9437ad66ba5d09f9acd4c72c66bde87'/>
<id>urn:sha1:aa65091bb9437ad66ba5d09f9acd4c72c66bde87</id>
<content type='text'>
Gets rid of the touch error message upon running the tests.
</content>
</entry>
<entry>
<title>MacOS: skip TestUtimesNanoSymlink and TestUtimesNanoFd</title>
<updated>2018-02-28T19:48:33+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-02-28T19:48:33+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=29496baa707e36d58bf97046a18b8ba0a4fc5bbc'/>
<id>urn:sha1:29496baa707e36d58bf97046a18b8ba0a4fc5bbc</id>
<content type='text'>
These cannot work on MacOS.
</content>
</entry>
<entry>
<title>fusefronted: add PlaintextNames special-cases for Create &amp; Rename</title>
<updated>2018-01-16T23:25:36+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2018-01-16T23:23:09+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=8951eb2472d6af50554806df2ffd655f53da8bfe'/>
<id>urn:sha1:8951eb2472d6af50554806df2ffd655f53da8bfe</id>
<content type='text'>
gocryptfs.longname.XXX files were considered magic in PlaintextNames
mode, which was wrong.

Fix that and add tests.

Fixes https://github.com/rfjakob/gocryptfs/issues/174
</content>
</entry>
<entry>
<title>fusefrontend: Handle PlaintextNames mode in Link</title>
<updated>2017-12-25T14:07:37+00:00</updated>
<author>
<name>Sebastian Lackner</name>
</author>
<published>2017-12-12T13:38:00+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a24342f656f6acd544ec07dada576d57a716b34d'/>
<id>urn:sha1:a24342f656f6acd544ec07dada576d57a716b34d</id>
<content type='text'>
In PlaintextNames mode the "gocryptfs.longname." prefix does not have any
special meaning.

https://github.com/rfjakob/gocryptfs/issues/174
</content>
</entry>
<entry>
<title>fusefrontend: Handle PlaintextNames mode in Unlink</title>
<updated>2017-11-28T08:28:06+00:00</updated>
<author>
<name>Sebastian Lackner</name>
</author>
<published>2017-11-28T00:22:55+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=2591900b6920a71f754779807bafeb01bfef5ab3'/>
<id>urn:sha1:2591900b6920a71f754779807bafeb01bfef5ab3</id>
<content type='text'>
In PlaintextNames mode the "gocryptfs.longname." prefix does not have any
special meaning. We should not attempt to delete any .name files.

Partially fixes https://github.com/rfjakob/gocryptfs/issues/174
</content>
</entry>
</feed>
