gocryptfs/tests/cli, branch v1.6.1 Mirror of gocryptfs source code on Github http://nuetzlich.net/cgit/gocryptfs/atom?h=v1.6.1 2018-08-11T21:26:49+00:00 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 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() main: accept -dev, -nodev, -suid, -nosuid, -exec, -noexec 2018-06-07T20:50:30+00:00 Jakob Unterwurzacher 2018-06-07T20:50:30+00:00 urn:sha1:53d6a9999dd0e4c31636d16179f284fff35a35d9 When mounted via /etc/fstab like this, /a /b fuse.gocryptfs default 0 0 we always get extra options passed. As reported by @mahkoh at https://github.com/rfjakob/gocryptfs/pull/233 : mount passes `-o noexec` if `-o user` is set and `-o exec` is not set. If both `-o user` and `-o exec` are set, it passes `-o exec`. Make these options work, and in addtion, also make -suid and -rw work the same way. Reported-by: @mahkoh main: make prefixOArgs errors testable 2018-06-05T19:02:35+00:00 Jakob Unterwurzacher 2018-06-05T19:02:35+00:00 urn:sha1:e29a81efc3df88b451a4a9464724a952d97b4115 By returning an error instead of calling os.Exit, error cases can be tested easily. Error cases were not tested until now. tests: cli_test: fix fd leak 2018-04-07T13:46:41+00:00 Jakob Unterwurzacher 2018-04-07T13:46:41+00:00 urn:sha1:9d7392a5be7e21aaaf2fb02f19b421c29e304632 One fd leak found in TestMountBackground. 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. main: add "-fsck" flag 2018-04-01T12:25:10+00:00 Jakob Unterwurzacher 2018-04-01T12:25:10+00:00 urn:sha1:8fcd39a3b08f956edc0939c87b089b4dbb60afd6 The fsck operation is not yet implemented, this commits just adds the flag and improves cli flag handling. 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 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. tests: check if we close stderr and stdout correctly on mount 2017-07-23T22:05:29+00:00 Jakob Unterwurzacher 2017-07-23T18:28:41+00:00 urn:sha1:318c41827cf23476b9705081f63b7f93fecba09a Currently fails, as reported at https://github.com/rfjakob/gocryptfs/issues/130 .