aboutsummaryrefslogtreecommitdiff
path: root/tests/example_filesystems/v2.2-xchacha-deterministic-names/QCVelV3GWR6e2tG6SEivxA
diff options
context:
space:
mode:
authorJakob Unterwurzacher2021-08-25 12:36:38 +0200
committerJakob Unterwurzacher2021-08-25 12:39:17 +0200
commit61ef6b00a675456ee05d40f1ce44d693bc4be350 (patch)
tree2ce32b48bb31ff728622d75e110075f5a43a7cf4 /tests/example_filesystems/v2.2-xchacha-deterministic-names/QCVelV3GWR6e2tG6SEivxA
parentb3d26b7264f3c025a48d19cb2784b83fc84a0ee4 (diff)
-devrandom: make flag a no-op
Commit f3c777d5eaa682d878c638192311e52f9c204294 added the `-devrandom` option: commit f3c777d5eaa682d878c638192311e52f9c204294 Author: @slackner Date: Sun Nov 19 13:30:04 2017 +0100 main: Add '-devrandom' commandline option 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. We now require Go v1.13 and Kernel versions should have also moved on. Make the flag a no-op. https://github.com/rfjakob/gocryptfs/issues/596
Diffstat (limited to 'tests/example_filesystems/v2.2-xchacha-deterministic-names/QCVelV3GWR6e2tG6SEivxA')
0 files changed, 0 insertions, 0 deletions