Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.4.4 2018-02-03T12:39:07+00:00 2018-02-03T12:39:07+00:00 Jakob Unterwurzacher 2018-02-03T12:39:07+00:00 urn:sha1:866e8508420374929c918485ac7336dc2be3aee7 The man page is rendered on github at https://github.com/rfjakob/gocryptfs/blob/master/Documentation/MANPAGE.md . Improve formatting a little. 2018-01-21T19:49:17+00:00 Jakob Unterwurzacher 2018-01-21T19:48:38+00:00 urn:sha1:7015a6ebfb530bad6b8ca5404b46599800917cd5 Also update the v1.4.3 release date to today. The release was delayed one day. 2018-01-21T19:04:37+00:00 Jakob Unterwurzacher 2018-01-21T19:04:37+00:00 urn:sha1:991708af016af074b4cd99b2bf333fc48effaa55 2018-01-20T12:35:26+00:00 Jakob Unterwurzacher 2018-01-20T12:35:26+00:00 urn:sha1:277ad087ffdc59e352c2e554caedc7a7796bbd2d Was unclear for new users - see https://github.com/rfjakob/gocryptfs/issues/194 2018-01-10T19:27:03+00:00 Felix Lechner 2018-01-10T19:27:03+00:00 urn:sha1:a4dff6aea0b761a49ba3f3b6f25b7442c846afcf Provide basic man page for xray tool 2018-01-10T08:26:48+00:00 Felix Lechner 2018-01-09T19:01:35+00:00 urn:sha1:63c3878b7cafd518514e7f3f7267af8bbd42bfd3 2017-12-05T21:54:08+00:00 Jakob Unterwurzacher 2017-12-05T21:53:40+00:00 urn:sha1:47b13e0a8d5d1e1312ba3fb70af318a0002780bf 2017-11-21T22:37:06+00:00 Sebastian Lackner 2017-11-19T12:30:04+00:00 urn:sha1:f3c777d5eaa682d878c638192311e52f9c204294 Allows to use /dev/random for generating the master key instead of the default Go implementation. When the kernel random generator has been properly initialized both are considered equally secure, however: * Versions of Go prior to 1.9 just fall back to /dev/urandom if the getrandom() syscall would be blocking (Go Bug #19274) * Kernel versions prior to 3.17 do not support getrandom(), and there is no check if the random generator has been properly initialized before reading from /dev/urandom This is especially useful for embedded hardware with low-entroy. Please note that generation of the master key might block indefinitely if the kernel cannot harvest enough entropy. 2017-11-12T19:06:13+00:00 Jakob Unterwurzacher 2017-11-12T19:06:13+00:00 urn:sha1:e36a0ebf189a826aaa63909c5518c16356f5f903 At the moment, it does two things: 1. Disable stat() caching so changes to the backing storage show up immediately. 2. Disable hard link tracking, as the inode numbers on the backing storage are not stable when files are deleted and re-created behind our back. This would otherwise produce strange "file does not exist" and other errors. Mitigates https://github.com/rfjakob/gocryptfs/issues/156 2017-10-19T20:04:46+00:00 Jakob Unterwurzacher 2017-10-19T20:04:46+00:00 urn:sha1:b3c20e512fc3eae27976853735d5e1554996cb62 ...if the filesystem was created with that option (or reverse mode). Mitigates https://github.com/rfjakob/gocryptfs/issues/148