Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v0.2 2015-10-11T16:33:28+00:00 2015-10-11T16:33:28+00:00 Jakob Unterwurzacher 2015-10-11T16:33:28+00:00 urn:sha1:d1d444435cf4351fc50ffd02c203cf4a2209b8e5 This prevents that the user enters the password only to get an error later. 2015-10-07T20:59:36+00:00 Jakob Unterwurzacher 2015-10-07T20:58:22+00:00 urn:sha1:ed1df49af5bb616e5ec34585b20c9c93a96b8088 2015-10-07T20:09:34+00:00 Jakob Unterwurzacher 2015-10-07T20:08:30+00:00 urn:sha1:440abcbac63a5994d4bac1b5dfcf838aaaefdbd7 ...also adapt the cryptfs tests for 256 bit long keys 2015-10-07T19:26:17+00:00 Jakob Unterwurzacher 2015-10-07T19:26:17+00:00 urn:sha1:65ba0739d5de756a437e0f840649583fa835a560 2015-10-06T20:27:37+00:00 Jakob Unterwurzacher 2015-10-06T20:27:37+00:00 urn:sha1:a3d286069f989dd16c6f91930a0df9fedfa2dd64 2015-10-06T18:51:35+00:00 Jakob Unterwurzacher 2015-10-06T18:51:35+00:00 urn:sha1:5c6df490678e7dc1aa7a09425d2fdf14fb13f7be AES-256 seems to be becoming the industry standard. While AES-128 is good enough for tens of years to come, let's follow suit and be extra safe. 2015-10-05T22:31:18+00:00 Jakob Unterwurzacher 2015-10-05T22:29:08+00:00 urn:sha1:022a6968ae0ede1259141e32b8e32553dad7d824 The shell wrapper sends gocryptfs into the background and waits for SIGUSR1 2015-10-04T21:58:22+00:00 Jakob Unterwurzacher 2015-10-04T21:55:58+00:00 urn:sha1:53ecebc71ec132fc8e5fab486c63e13c0925d142 2015-10-04T19:36:16+00:00 Jakob Unterwurzacher 2015-10-04T19:36:16+00:00 urn:sha1:e6b7353f4e9516a712d7cd9dab7d73c6c79ae7d0 The old implementation of counting up from a random starting point had the problem that is allowed an attacker to find out the write order of the blocks. 2015-10-04T12:49:47+00:00 Jakob Unterwurzacher 2015-10-04T12:36:20+00:00 urn:sha1:89fef80d32708874c95742db0a7b593bcfd3b31d