gocryptfs/internal/configfile, branch v1.6 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.6 2018-07-23T20:25:40+00:00 configfile: drop superflous Printf 2018-07-23T20:25:40+00:00 Jakob Unterwurzacher 2018-07-23T20:24:19+00:00 urn:sha1:f4a972ddf1f8002095b1e57bd93bb8894ae745f2 Before: $ gocryptfs -fsck . LoadConfFile: ReadFile: &os.PathError{Op:"open", Path:"/var/tmp/check-gocryptfs/scratchdev/gocryptfs.conf", Err:0xd} Cannot open config file: open /var/tmp/check-gocryptfs/scratchdev/gocryptfs.conf: permission denied After: $ gocryptfs -fsck . Cannot open config file: open /var/tmp/check-gocryptfs/scratchdev/gocryptfs.conf: permission denied Only print masterkey once on -init 2018-07-01T18:56:22+00:00 Jakob Unterwurzacher 2018-06-26T18:44:10+00:00 urn:sha1:6d64dfe8f7acd8e9ca4a659d26318e442c2db85a It is no longer printed at all when mounting a filesystem, printing on -init can be disabled with -q. https://github.com/rfjakob/gocryptfs/issues/76 trezor: add TrezorPayload 2018-07-01T18:56:22+00:00 Jakob Unterwurzacher 2018-06-25T20:27:15+00:00 urn:sha1:9a15dfa494c76b5fcadcd32e2e46cbee84218a87 TrezorPayload stores 32 random bytes used for unlocking the master key using a Trezor security module. The randomness makes sure that a unique unlock value is used for each gocryptfs filesystem. configfile: reduce function name stutter 2018-07-01T18:56:22+00:00 Jakob Unterwurzacher 2018-06-25T20:02:05+00:00 urn:sha1:91de77943fba3cb993aad4e9756e159c4514764a configfile.LoadConfFile() -> configfile.Load() configfile.CreateConfFile() -> configfile.Create() 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. configfile: use tlog.ColorYellow instead of hardcoded color code 2018-06-24T17:52:47+00:00 Jakob Unterwurzacher 2018-06-24T17:51:05+00:00 urn:sha1:743c7705b21575fe97e5da5722ec344c76badd60 fsck: test against example_filesystems 2018-04-02T16:43:50+00:00 Jakob Unterwurzacher 2018-04-02T16:43:50+00:00 urn:sha1:a0fd3eca98218aa7d165080ab20cf234330e5e09 readpassword: convert from string to []byte 2018-02-18T13:26:54+00:00 Jakob Unterwurzacher 2018-02-18T13:26:54+00:00 urn:sha1:3b8f5cbb17c964224456bb36b096feafb0e24f44 This will allows us to overwrite the password with zeros once we are done with it. https://github.com/rfjakob/gocryptfs/issues/211 configfile: overwrite and let keys run out of scope 2018-02-18T11:39:44+00:00 Jakob Unterwurzacher 2018-02-18T11:37:37+00:00 urn:sha1:0efd220d1e10ac8e3d0048ff4d068cc8174e7185 As soon as we don't need them anymore, overwrite keys with zeros and make sure they run out of scope so we don't create a risk of inadvertedly using all-zero keys for encryption. https://github.com/rfjakob/gocryptfs/issues/211 main: Add '-devrandom' commandline option 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.