gocryptfs/internal/exitcodes, branch v2.0 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v2.0 2020-09-12T16:06:54+00:00 Add support for FIDO2 tokens 2020-09-12T16:06:54+00:00 Pavol Rusnak 2020-09-05T20:42:15+00:00 urn:sha1:1e624a4cc3aafa57b5fa213c88bcd3689cefd1c3 remove Trezor support 2019-12-28T18:50:49+00:00 Pavol Rusnak 2019-12-27T21:27:57+00:00 urn:sha1:1364b44ae356da31e24e5605fe73a307e9d6fb03 main: ensure fds 0,1,2 are always open 2019-01-05T13:17:51+00:00 Jakob Unterwurzacher 2019-01-05T13:12:00+00:00 urn:sha1:ad15ad99856f90f3a72be4bd22ce44338645c963 The Go stdlib, as well as the gocryptfs code, relies on the fact that fds 0,1,2 are always open. See https://github.com/rfjakob/gocryptfs/issues/320 for details. Assorted spelling fixes. 2018-12-27T14:19:55+00:00 Sebastian Lackner 2018-12-27T11:03:00+00:00 urn:sha1:874eaf9734cc10940e08f7b043652449e1e220b5 Mostly detected with the 'codespell' utility, but also includes some manual grammar fixes. reverse mode: add --exclude option 2018-08-11T21:26:49+00:00 Jakob Unterwurzacher 2018-08-11T21:26:49+00:00 urn:sha1:ec2fdc19cf9358ae7ba09c528a5807b6b0760f9b https://github.com/rfjakob/gocryptfs/issues/235 trezor: add skeleton for Trezor support 2018-07-01T18:56:04+00:00 Jakob Unterwurzacher 2018-06-17T13:25:09+00:00 urn:sha1:c6f6e8ec4d71475a24ebbb0e64f19ad94249efd9 readpassword.Trezor() is not implemented yet and returns a hardcoded dummy key. fsck: test against example_filesystems 2018-04-02T16:43:50+00:00 Jakob Unterwurzacher 2018-04-02T16:43:50+00:00 urn:sha1:a0fd3eca98218aa7d165080ab20cf234330e5e09 fsck: add initial implementation 2018-04-02T14:38:18+00:00 Jakob Unterwurzacher 2018-04-01T19:23:32+00:00 urn:sha1:f28d85fad599ffaef9a8e1f353911c81a6605d2f Most corruption cases except xattr should be covered. With test filesystem. The output is still pretty ugly. xattr support will be added in the next commits. Add "-trace" flag (record execution trace) 2017-06-07T20:09:06+00:00 Jakob Unterwurzacher 2017-06-05T20:45:11+00:00 urn:sha1:71978ec88a2aa8ec92df080a4a6becf623957c81 Uses the runtime/trace functionality. TODO: add to man page. main: downgrade panic log create failure from fatal error to warning 2017-05-23T16:01:21+00:00 Jakob Unterwurzacher 2017-05-23T16:01:21+00:00 urn:sha1:508fd9e1d64131958c86175cb8d848f730e629cf Exiting with a fatal error just pushes users to use "-nosyslog", which is even worse than not having a paniclog.