summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/randomness_seeding.mdwn
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2016-09-01 15:36:19 +0200
committeramnesia <webmaster@amnesia.boum.org>2016-09-01 15:36:19 +0200
commiteffe34be113ad97fb731d36545a772b900358bb2 (patch)
treedad3a3a0b48a01841e7353e99daad4a0ece70a4f /wiki/src/blueprint/randomness_seeding.mdwn
parent941b9c0be9998b2675a53abca22db8874723b5b9 (diff)
fixed typo's
Diffstat (limited to 'wiki/src/blueprint/randomness_seeding.mdwn')
-rw-r--r--wiki/src/blueprint/randomness_seeding.mdwn10
1 files changed, 5 insertions, 5 deletions
diff --git a/wiki/src/blueprint/randomness_seeding.mdwn b/wiki/src/blueprint/randomness_seeding.mdwn
index 89804c2..4c4302f 100644
--- a/wiki/src/blueprint/randomness_seeding.mdwn
+++ b/wiki/src/blueprint/randomness_seeding.mdwn
@@ -1,6 +1,6 @@
# /dev/random and /dev/urandom radomness seeding in Tails
-/dev/random and /dev/urandom are especial Linux devices that provide access from user land
+/dev/random and /dev/urandom are special Linux devices that provide access from user land
to the Linux kernel Pseudo Random Number Generator (PRNG). This generator is used for almost
every security protocol, like TLS/SSL key generation, choosing TCP sequence and file system and email
encryption [1]. Such PRNG requires a a "good" source of randomness on initialization,
@@ -36,9 +36,9 @@ problem for the first time Tails is booted.
### Use a stronger entropy collector library [[!tails_ticket 5650]]
-We could try haveged as well as other entropy collection daemons. It would be nice to
-have study (read: a survey of packages, etc) of all the useful entropy gathering daemons
-that might be of use on a Tails system.
+We could try `haveged` as well as other entropy collection daemons. It would be nice to
+have a study (read: a survey of packages, etc) of all the useful entropy gathering daemons
+that might be of use on a Tails system. (XXX)
### Use the Tails installer to create a better seed
@@ -47,7 +47,7 @@ Windows and OSX, we could use their PRNG to generate a presumably better
seed file on every new Tails installation. Of course this should be a post installation
mechanism, after verifying the ISO/disk image hash/signature.
-This would at least provide a better escenario than the one with the same known
+This would at least provide a better scenario than the one with the same known
and constant seed file, which provides entropy zero.
This solution is partial since it only works for Tails Installer+USB stick, and doesn't