emo/ndhc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6047f04a12
ndhc/src/duiaid.h

37 lines
1.6 KiB
C
Raw Normal View History

Support RFC4361. RFC4361 requires clients to send a clientid, and specifies that by default that clientid should be a combination of a machine-static DUID and an interface-static IAID. There are several RFC-compliant DUIDs. ndhc uses RFC6355's DUID-UUID, but chooses not to follow RFC4122 for the UUID and instead simply uses random bytes from its combined Tausworthe PRNG. RFC4122 is excessively complex, and 128-bit random values are more than sufficiently collision-resistant on even large DHCP segments. ndhc requires a read/writable directory to store the DUID/IAID states. By default this directory is /etc/ndhc. It exists outside the chroot. The DUID will be stored in a single file, DUID. The IAIDs exist per-interface and are stored in files with names similar to IAID-xx:xx:xx:xx:xx:xx, where the xx values are replaced by the Ethernet hardware address of the interface. If it is impossible to read or store the DUIDs or IAIDs, ndhc will fail at start time before it performs any network activity or forks any subprocesses. If the host system lacks volatile storage, then a clientid should manually be specified using the -c or --clientid command arguments.
2014-03-19 10:12:32 +05:30
/* duiaid.h - DUID/IAID storage and generation for clientids
*
Replace '(c)' with 'Copyright'. '(c)' may not be a valid substitute for 'Copyright' in some legal domains/interpretations. So be safe, since I obviously am asserting copyright on my legal work.
2018-10-26 16:41:16 +05:30
* Copyright 2014-2018 Nicholas J. Kain <njkain at gmail dot com>
Support RFC4361. RFC4361 requires clients to send a clientid, and specifies that by default that clientid should be a combination of a machine-static DUID and an interface-static IAID. There are several RFC-compliant DUIDs. ndhc uses RFC6355's DUID-UUID, but chooses not to follow RFC4122 for the UUID and instead simply uses random bytes from its combined Tausworthe PRNG. RFC4122 is excessively complex, and 128-bit random values are more than sufficiently collision-resistant on even large DHCP segments. ndhc requires a read/writable directory to store the DUID/IAID states. By default this directory is /etc/ndhc. It exists outside the chroot. The DUID will be stored in a single file, DUID. The IAIDs exist per-interface and are stored in files with names similar to IAID-xx:xx:xx:xx:xx:xx, where the xx values are replaced by the Ethernet hardware address of the interface. If it is impossible to read or store the DUIDs or IAIDs, ndhc will fail at start time before it performs any network activity or forks any subprocesses. If the host system lacks volatile storage, then a clientid should manually be specified using the -c or --clientid command arguments.
2014-03-19 10:12:32 +05:30
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions are met:
*
* - Redistributions of source code must retain the above copyright notice,
* this list of conditions and the following disclaimer.
*
* - Redistributions in binary form must reproduce the above copyright notice,
* this list of conditions and the following disclaimer in the documentation
* and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*/
#ifndef NJK_NDHC_DUIAID_H_
#define NJK_NDHC_DUIAID_H_
#include "ndhc.h"
Mark pointer arguments that cannot ever be null as [static 1]. Also constify some cases, too.
2015-02-14 09:44:08 +05:30
void get_clientid(struct client_state_t cs[static 1],
struct client_config_t cc[static 1]);
Support RFC4361. RFC4361 requires clients to send a clientid, and specifies that by default that clientid should be a combination of a machine-static DUID and an interface-static IAID. There are several RFC-compliant DUIDs. ndhc uses RFC6355's DUID-UUID, but chooses not to follow RFC4122 for the UUID and instead simply uses random bytes from its combined Tausworthe PRNG. RFC4122 is excessively complex, and 128-bit random values are more than sufficiently collision-resistant on even large DHCP segments. ndhc requires a read/writable directory to store the DUID/IAID states. By default this directory is /etc/ndhc. It exists outside the chroot. The DUID will be stored in a single file, DUID. The IAIDs exist per-interface and are stored in files with names similar to IAID-xx:xx:xx:xx:xx:xx, where the xx values are replaced by the Ethernet hardware address of the interface. If it is impossible to read or store the DUIDs or IAIDs, ndhc will fail at start time before it performs any network activity or forks any subprocesses. If the host system lacks volatile storage, then a clientid should manually be specified using the -c or --clientid command arguments.
2014-03-19 10:12:32 +05:30
#endif /* NJK_NDHC_DUIAID_H_ */
Reference in New Issue Copy Permalink