[rt27912]
Add code to suppor on {commit expiry release} statements for DHCPv6.
There are several pieces to this change
1) Add space in the iasubopt structure to hold the statement pointers
2) Update the execute code to fill in the structures as necessary
3) Execute the statements when appropriate
Many of the changes in the non-v6 code are to pass the v6 structures
around to the execute code.
[rt26311]
Fix the issue with DDNS by checking to see if we have added a pointer
to the ddns_cb and skipping the cache threshold check if we did. Also
expand and correct the cache threshold check into the delayed ack code.
Squashed commit of the following:
[rt33351]
Check for overly long whitespace in files we are parsing and
print a message and exit if we find it. We could try and continue
but given that the file is likely corrupt that doesn't seem useful.
commit e5cde5645b6cdeee04761fa3671d9e9f3b5abdd4
commit 25c632ab85e996f89a8e0337a3c5caef6ff4392a
remove repeated words
fix: it's to its
some minor formatting added
(this needs to be improved still, there is a mix
of \fB Bold and \fI underline for same things)
spelling fixes
minor punctuation fixes (remove ...)
uppercase an acronym that is not a config item
(I didn't get this reviewed, these all are very minor or obvious.)
Relax the requirements for deleting an A or AAAA record.
Previously the DDNS removal code required both the A or AAAA
record and the TXT record to exist. This requirement could
cause problems if something interrupted the removal leaving
the TXT record alone. This relaxation was codified in RFC 4703.
[ISC-Bugs #30734]
make check no longer tries to run atf when ATF was not enabled
(make check target does not make much sense with tests disabled,
but it shouldn't fail complaining about missing atf-run)
[rt29770]
[rt29846]
Tidy up man pages, mostly convert a period followed by 1
or 3 spaces to a period followed by 2 spaces. This also
covers tickets 29770 and 29846
Squashed commit of the following:
commit d40674fdfc8a81a44f8033bf048587a3eab0471f
Author: Shawn Routhier <sar@isc.org>
Date: Fri Aug 3 17:55:05 2012 -0700
length client ids to be processed. Under some situations use of
zero length client ids can cause the server to go into an infinite
loop. As such ids are not valid according to RFC 2132 section 9.14
the server no longer accepts them. Client ids with a length of 1
are also invalid but the server still accepts them in order to
minimize disruption. The restriction will likely be tightened in
the future to disallow ids with a length of 1.
Thanks to Markus Hietava of Codenomicon CROSS project for the
finding this issue and CERT-FI for vulnerability coordination.
[ISC-Bugs #29851]
CVE: CVE-2012-3571
was used is now solved on GNU/Linux, BSD and GNU/Hurd systems. Note
that use-sockets feature was not tested on those systems. Client and
server code no longer use MAX_PATH constant that is not defined on
GNU/Hurd systems. [ISC-Bugs 25979]
[ISC-Bugs #22625] - properly print options that have several fields
followed by an array of something for example "fIa"
[ISC-Bugs #27289] - properly parse options in declarations that have
several fields followed by an array of something for example "fIa"
[ISC-Bugs #27296] - properly determine if we parsed a 16 or 32 bit
value in evaluate_numeric_expression (extract-int).
[ISC-Bugs #27314] - properly parse a zero length option from
a lease file. Thanks to Marius Tomaschewski from SUSE for the report
and prototype patch for this ticket as well as ticket 27289.
relay code. We've tested this on Solaris and hope to expand
support for Infiniband in the future. This patch also corrects
some issues we found in the socket code. [ISC-Bugs #24245]
