emo/ndhc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation update.

Browse Source
This commit is contained in:
Nicholas J. Kain 2015-01-10 18:34:51 -05:00
parent 9f87bd8b30
commit 6f6aad211e
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README
View File

@ -1,4 +1,4 @@
ndhc, Copyright (C) 2004-2014 Nicholas J. Kain. ndhc, Copyright (C) 2004-2015 Nicholas J. Kain.
See LICENSE for licensing information. In short: Two-clause / New BSD. See LICENSE for licensing information. In short: Two-clause / New BSD.
Requirements: Requirements:
@ -77,6 +77,7 @@ Flexible. ndhc can request particular IPs, send user-specified client IDs,
write a file that contains the current lease IP, write PID files, etc. write a file that contains the current lease IP, write PID files, etc.
Self-contained. ndhc does not exec other processes, or rely on the shell. Self-contained. ndhc does not exec other processes, or rely on the shell.
Further, ndhc relies on no external libraries aside from the system libc.
Aware of the hardware link status. If you disconnect an interface on which Aware of the hardware link status. If you disconnect an interface on which
ndhc is providing dhcp service, it will be aware. When the link status ndhc is providing dhcp service, it will be aware. When the link status
@ -186,9 +187,9 @@ be specified using the -I or --clientid command arguments.
RANDOMNESS NOTES RANDOMNESS NOTES
---------------- ----------------
Each ndhc subprocess maintains a combined Tausworthe PRNG that is uniquely Each ndhc subprocess maintains a PCG PRNG that is uniquely seeded from the
seeded from the kernel random device at startup. Each PRNG consumes 128 bits kernel random device at startup. Each PRNG consumes 128 bits of entropy for
of entropy for its initial state. its initial state.
DHCP does not require cryptographic randomness, so this arrangement should DHCP does not require cryptographic randomness, so this arrangement should
be more than sufficient to ensure proper UUIDs, assuming only that the be more than sufficient to ensure proper UUIDs, assuming only that the