<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/tests/example_filesystems, branch det</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=det</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=det'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2017-05-28T17:02:22+00:00</updated>
<entry>
<title>tests: add v1.3-reverse example filesystem</title>
<updated>2017-05-28T17:02:22+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-05-28T17:02:22+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=1f5201da5ebb0180717f63d77bbe2338876bfd29'/>
<id>urn:sha1:1f5201da5ebb0180717f63d77bbe2338876bfd29</id>
<content type='text'>
We check the md5 sum of the encrypted version of a file to make sure we don't
accidentially change the ciphertext generation.
</content>
</entry>
<entry>
<title>cli: enable "-raw64" by default</title>
<updated>2017-03-07T19:56:50+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-06T21:59:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=efc88346bec52675d5243f988aa3386d617ee1c4'/>
<id>urn:sha1:efc88346bec52675d5243f988aa3386d617ee1c4</id>
<content type='text'>
This brings the CLI options back in sync with the default
feature flags.
</content>
</entry>
<entry>
<title>tests: recreate v1.3 example filesystem</title>
<updated>2017-03-07T19:56:50+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-06T21:53:49+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=f1244b6d06a4932e8a51adedf351ec83262c2db5'/>
<id>urn:sha1:f1244b6d06a4932e8a51adedf351ec83262c2db5</id>
<content type='text'>
The filesystem was created with a gocryptfs version that ignored
the HKDF flag (hence everything was actually encrypted WITHOUT hkdf).

Fix it by recreating it.
</content>
</entry>
<entry>
<title>cli: add "-hkdf" option</title>
<updated>2017-03-07T19:56:50+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-06T21:43:55+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=2362e67a9e5c6f1c96e987e8753eca295f283875'/>
<id>urn:sha1:2362e67a9e5c6f1c96e987e8753eca295f283875</id>
<content type='text'>
This commit also enables actually passing the HKDF setting to
fusefrontend, this was missing till now.
</content>
</entry>
<entry>
<title>tests: add v1.3 example filesystem</title>
<updated>2017-03-05T22:07:52+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-05T22:06:40+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=b7538fc026dc25d0061e08bedc4b3aff97bb52d2'/>
<id>urn:sha1:b7538fc026dc25d0061e08bedc4b3aff97bb52d2</id>
<content type='text'>
This filesystem has both HKDF and Raw64 enabled.
</content>
</entry>
<entry>
<title>Drop Go 1.4 compatability code everywhere</title>
<updated>2017-03-05T16:44:14+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-05T16:44:14+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=966308eeb7793a4a8ca578e160981e3b059b82e6'/>
<id>urn:sha1:966308eeb7793a4a8ca578e160981e3b059b82e6</id>
<content type='text'>
Yields a nice reduction in code size.
</content>
</entry>
<entry>
<title>tests: stop calling t.Fatal from example_test_helpers</title>
<updated>2017-03-05T12:39:25+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-03-05T12:39:25+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=b2f154a9a908e6ec097de90c04ce45118adc76de'/>
<id>urn:sha1:b2f154a9a908e6ec097de90c04ce45118adc76de</id>
<content type='text'>
Calling t.Fatal immeadiately aborts the test, which means the
filesystem will not get unmounted, which means test.bash will
hang.
</content>
</entry>
<entry>
<title>tests: somewhat support testing without openssl</title>
<updated>2017-02-26T18:53:29+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2017-02-26T18:53:29+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d2c0fae4f657d01b692d04056f997c611b96299b'/>
<id>urn:sha1:d2c0fae4f657d01b692d04056f997c611b96299b</id>
<content type='text'>
You will still get lots of test error, but at least the tests
will run.
</content>
</entry>
<entry>
<title>tests: don't call t.Fatal in checkExampleFS</title>
<updated>2016-11-26T14:20:54+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-11-26T14:17:15+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=3f5c48e0585f6fe0782aded541e42879eb570e69'/>
<id>urn:sha1:3f5c48e0585f6fe0782aded541e42879eb570e69</id>
<content type='text'>
Calling t.Fatal means that the parent test has no chance
to clean up.
</content>
</entry>
<entry>
<title>reverse: gocryptfs.conf was missing from the directory listings</title>
<updated>2016-10-08T20:25:08+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-10-08T20:25:08+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=d25fcc6a4b095e37c77cce8f9de2ec0f12007ed5'/>
<id>urn:sha1:d25fcc6a4b095e37c77cce8f9de2ec0f12007ed5</id>
<content type='text'>
Fix the test for that and add checks in example_filesystems_test.
</content>
</entry>
</feed>
