<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gocryptfs/internal, branch v0.10</title>
<subtitle>Mirror of gocryptfs source code on Github</subtitle>
<id>http://nuetzlich.net/cgit/gocryptfs/atom?h=v0.10</id>
<link rel='self' href='http://nuetzlich.net/cgit/gocryptfs/atom?h=v0.10'/>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/'/>
<updated>2016-05-30T07:36:06+00:00</updated>
<entry>
<title>fusefrontend: replace unreliable "fd &lt; 0" check</title>
<updated>2016-05-30T07:36:06+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-30T07:29:30+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=5dd9576a11bb166e5b3cad70047a46038daf32d6'/>
<id>urn:sha1:5dd9576a11bb166e5b3cad70047a46038daf32d6</id>
<content type='text'>
... with the "released" boolean.

For some reason, the "f.fd.Fd() &lt; 0" check did not work reliably,
leading to nil pointer panics on the following wlock.lock().

The problem was discovered during fsstress testing and is unlikely
to happen in normal operations.

With this change, we passed 1700+ fsstress iterations.
</content>
</entry>
<entry>
<title>toggledlog: wpanic: use Logger.Panic instead of naked panic</title>
<updated>2016-05-30T07:26:59+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-30T07:26:59+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=5e9953ec27979675160f45a5824ac727f5c5cd50'/>
<id>urn:sha1:5e9953ec27979675160f45a5824ac727f5c5cd50</id>
<content type='text'>
This makes sure the panic message also ends up in syslog
(if enabled).
</content>
</entry>
<entry>
<title>fusefrontend: use sync.Once for one-time warnings</title>
<updated>2016-05-29T20:50:03+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-29T20:50:03+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=1648c54adb9b7d9d8984857a35c6092bbae6bdec'/>
<id>urn:sha1:1648c54adb9b7d9d8984857a35c6092bbae6bdec</id>
<content type='text'>
Using a simple boolean was racy (which was harmless
in this case) and non-idomatic.
</content>
</entry>
<entry>
<title>fusefronted: check Fstat return value on file create</title>
<updated>2016-05-29T20:43:48+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-29T20:41:46+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=fd53dfd2ad88d9d277e5ab93fba1b81a5f2255d4'/>
<id>urn:sha1:fd53dfd2ad88d9d277e5ab93fba1b81a5f2255d4</id>
<content type='text'>
The Fstat call should never fail, but still, if it does return an error
it should be handled properly.
</content>
</entry>
<entry>
<title>fusefrontend: simplify wlockMap</title>
<updated>2016-05-29T20:40:05+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-29T20:40:05+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=77813bdc13118fd08bbff7a68c9d5268080a2a15'/>
<id>urn:sha1:77813bdc13118fd08bbff7a68c9d5268080a2a15</id>
<content type='text'>
mapMutex can be anonymous and using an RWMutex is overkill
because the lock protects very short sections.
</content>
</entry>
<entry>
<title>fusefrontend: remove unused "forgotten" variable</title>
<updated>2016-05-29T11:46:47+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-29T11:46:47+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4c0cb37c50c66b03be43063d77a52b74f24ec9f7'/>
<id>urn:sha1:4c0cb37c50c66b03be43063d77a52b74f24ec9f7</id>
<content type='text'>
The functionality has long been replaced by the fd &lt; 0
check.
</content>
</entry>
<entry>
<title>stupidgcm: add benchmark.bash wrapper</title>
<updated>2016-05-22T13:49:09+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-22T13:49:09+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=888e147cd8698ad13ddec6c5e35ca928ff701a7e'/>
<id>urn:sha1:888e147cd8698ad13ddec6c5e35ca928ff701a7e</id>
<content type='text'>
Add a simple bash wrapper to make it easier to run the GCM
benchmarks.
</content>
</entry>
<entry>
<title>Encrypt path in statfs() calls</title>
<updated>2016-05-12T21:24:39+00:00</updated>
<author>
<name>David Gnedt</name>
</author>
<published>2016-05-12T17:51:13+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=a93bcabe9c1dea14bf29b94cbddf62c1bec4d315'/>
<id>urn:sha1:a93bcabe9c1dea14bf29b94cbddf62c1bec4d315</id>
<content type='text'>
Paths in statfs() calls were not encrypted resulting in
an Function not implemented error, when the unencrypted
path didn't exist in the underlying (encrypted)
filesystem.

$ df plain/existingdir
df: ‘plain/existingdir’: Function not implemented
</content>
</entry>
<entry>
<title>prefer_openssl: add amd64 constraint</title>
<updated>2016-05-12T07:50:36+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-12T07:50:36+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=4ad9d4e444e4f75fd388078b617c411bfab762c8'/>
<id>urn:sha1:4ad9d4e444e4f75fd388078b617c411bfab762c8</id>
<content type='text'>
Optimized assembly versions for Go GCM are only available
on amd64.
</content>
</entry>
<entry>
<title>prefer_openssl: autodetect whether to use OpenSSL or Go GCM</title>
<updated>2016-05-11T22:42:42+00:00</updated>
<author>
<name>Jakob Unterwurzacher</name>
</author>
<published>2016-05-11T21:36:57+00:00</published>
<link rel='alternate' type='text/html' href='http://nuetzlich.net/cgit/gocryptfs/commit/?id=49b597f07c07bde6a2feb1f32f02fcaf34daf365'/>
<id>urn:sha1:49b597f07c07bde6a2feb1f32f02fcaf34daf365</id>
<content type='text'>
Go GCM is faster than OpenSSL if the CPU has AES instructions
and you are running Go 1.6+.

The "-openssl" option now defaults to "auto".

"gocryptfs -debug -version" displays the result of the autodetection.

See https://github.com/rfjakob/gocryptfs/issues/23 for details and
benchmarks.
</content>
</entry>
</feed>
