diff options
Diffstat (limited to 'RELNOTES')
| -rw-r--r-- | RELNOTES | 726 |
1 files changed, 702 insertions, 24 deletions
@@ -1,10 +1,8 @@ - Internet Software Consortium DHCP Distribution - Version 3.1, Working Branch + Internet Systems Consortium DHCP Distribution + Version 3.1 - HEAD + March 3, 2005 - Release Notes - -This is a development snapshot of Version 3 of the Internet Software -Consortium DHCP Distribution. + Release Notes NEW FEATURES @@ -24,19 +22,9 @@ that are new since version 2.0: - Many bug fixes, performance enhancements, and minor new DHCP protocol features. -This release has been beta tested quite thorougly, and we think it is -substantially more robust at this time than 2.0pl5. The release -candidate is expected to be free of serious bugs, but it's called a -release candidate because we want people to try it and find any last -real problems before we call it done. We do not expect to add -anything other than documentation and any remaining bug fixes to the -3.0 release. - -The 3.0 Release Candidate 1 lease file is not backwards compatible -with the 3.0 Beta 1 lease file, so if you have to go back, you will -have to convert your lease files back to the 3.0 Beta 1 format - if -you try to run a 3.0 Beta 1 server on a 3.0 lease file, it will -cheerfully delete all your leases. +The main bug fixed here is a bug in the subclass allocation code that +could result in a memory smash. Any users of the ISC DHCP server who +are using subclasses should seriously consider upgrading to 3.0.1. If you are running 3.0 beta 1 and are doing dynamic DNS updates, the lease file is no longer forward-compatible to 3.0 final. A script @@ -55,6 +43,696 @@ Murrell at BC Tel Advanced Communications. I'd like to express my thanks to all of these good people here, both for working on the code and for prodding me into improving it. + + Changes since 3.0 (New Features) + +- A workaround for certain STSN servers that send a mangled domain-name + option was introduced for dhclient. The client will now accept corrupted + server responses, if they contain a valid DHCP_MESSAGE_TYPE (OFFER, ACK, + or NAK). The server will continue to not accept corrupt client packets. + +- Support for 'reserved' (static) and BOOTP leases via failover was + introduced. + +- Support for adding, removing, and managing class and subclass statements + via OMAPI. + +- 'make install' now creates the initial zero-length dhcpd.leases file if + one does not already exist on the system. + +X The 'www-server' option was documented. This should probably be + backported to V3-RELEASE-BRANCH. + + + Changes since 3.0.2 + +- A bug was fixed where a server might load balance a DHCP REQUEST to its + peer after already choosing not to load balance the preceeding DISCOVER. + The peer cannot allocate the originating server's lease. + +- In the case where a secondary server lost its stable storage while the + primary was still in communications-interrupted, and came back online, + the lease databases would not be fully transferred to the secondary. + This was due to the secondary errantly sending an extra UPDREQ message + when the primary made its state transition to PARTNER-DOWN known. + +- The package will now compile cleanly in gcc 3.3 and 3.4. As a side effect, + lease structures will be 9 bytes smaller on all platforms. Thanks to + Jason Vas Dias at Redhat. + +- Interface discovery code in DISCOVER_UNCONFIGURED mode is now + properly restricted to only detecting broadcast interfaces. Thanks + to a patch from Jason Vas Dias at RedHat. + +- decode_udp_ip_header was changed so that the IP address was copied out + to a variable, rather than referenced by a pointer. This enforces 4-byte + alignment of the 32-bit IP address value. Thanks to a patch from Dr. + Peter Poeml. + +- An incorrect log message was corrected thanks to a patch from + Dr. Peter Poeml. + +- A bug in DDNS was repaired, where if the server's first DDNS action was + a DDNS removal rather than a DDNS update, the resolver library's + retransmit timer and retry timer was set to the default, implying a + 15 second timeout interval. Which is a little excessive in a synchronous, + single-threaded system. In all cases, ISC DHCP should now hold fast to + a 1-second timeout, trying only once. + +- The siaddr field was being improperly set to the server-identifier when + responding to DHCP messages. RFC2131 clarified the siaddr field as + meaning the 'next server in the bootstrap process', eg a tftp server. + The siaddr field is now left zeroed unless next-server is configured. + +- mockup_lease() could have returned in an error condition (or in the + condition where no fixed-address was found matching the shared + network) with stale references to a host record. This is probably not + a memory leak since host records generally never die anyway. + +- A bug was repaired where failover servers would let stale client identifiers + persist on leases that were reallocated to new clients not sending an id. + +- Binding scopes ("set var = value;") are now removed from leases allocated + by failover peers if the lease had expired. This should help reduce the + number of stale binding scopes on leases. + +- A small memory leak was closed involving client identifiers larger than + 7 bytes, and failover. + +- Configuring a subnet in dhcpd.conf with a subnet mask of 32 bits might + cause an internal function to overflow heap. Thanks to Jason Vas Dias + at Redhat. + +- Some inconsistencies in treating numbers that the lexer parsed as 'NUMBER' + or 'NUMBER_OR_NAME' was repaired. Hexadecimal parsing is affected, and + should work better. + +- In several cases, parse warnings were being issued before the lexical + token had been advanced to the token whose value was causing an error... + causing parse warnings to claim the problem is on the wrong token. + +- Host declarations matching on client identifier for dynamic leases will + no longer match fixed-address host declarations (this is now identical + to behaviour for host records matching on hardware address). + + Changes since 3.0.2rc3 + +- A previously undocumented configuration directive, 'local-address', + was documented in the dhcpd.conf manpage. + + Changes since 3.0.2rc2 + +- Two varaibles introduced in 3.0.2b1 were used without being initialized + in the case where neither the FILE nor SNAME fields were available for + overloading. This was repaired. + +- A heretofore believed to be impossible corner case of the option + overloading implementation turned out to be possible ("Unable to sort + overloaded options after 10 tries."). The implementation was reworked + to consider the case of an option so large it would require more than + three chunks to fit. + +- Many other instances of variables being used without being initialized + were repaired. + +- An uninitialized variable in omapi_io_destroy() led to the discovery + that this function may result in orphaned pointers (and hence, a memory + leak). + + Changes since 3.0.2rc1 + +- allocate_lease() was rewritten to repair a bug in which the server would + try to allocate an ABANDONED lease when FREE leases were available. + + Changes since 3.0.2b1 + +- Some dhcp-eval.5 manpage formatting was repaired. + + Changes since 3.0.1 + +- A bug was fixed in the server's 'option overloading' implementation, + where options loaded into the 'file' and 'sname' packet fields were + not aligned precisely as rfc2131 dictates. + +- The FreeBSD client script was changed to support the case where a domain + name was not provided by the server. + +- A memory leak in 'omshell' per each command line parsed was + repaired, thanks to a patch from Jarkko Torppa. + +- Log functions writing to stderr were adjusted to use the STDERR_FILENO + system definition rather than '2'. This is a no-op for 90% of platforms. + +- One call to trace_write_packet_iov() counted the number of io vectors + incorrectly, causing inconsistent tracefiles. This was fixed. + +- Some expression parse failure memory leaks were closed. + +- A host byte order problem in tracefiles was repaired. + +- Pools configured in DHCPD for failover possessing permission lists that + previously were assumed to not include dyanmic bootp clients are now + a little more pessimistic. The result is, dhcpd will nag you about just + about most pools that possess a 'allow' statement with no 'deny' that + would definitely match a dynamic bootp client. + +- The 'ddns-update-style' configuration warning bit now insists that + the configuration be globally scoped. + +- Two memory leaks in dhclient were closed thanks to a patch from Felix + Farkas. + +- Some minor but excellently pedantic documentation errors were fixed + thanks to a patch from Thomas Klausner. + +- Bugs in operator precedence in executable statements have been repaired + once again. More legal syntaxes should be parsed legally. + +- Failing to initialize a tracefile for any reason if a tracefile was + specified is now a fatal error. Thanks to a patch from Albert Herranz. + +- Corrected a bug in which the number of leases transferred as calculated + by the failover primary and sent to peers in POOLRESP responses may be + incorrect. This value is not believed to be used by other failover + implementations, excepting perhaps as logged information. + +- Corrected a bug in which 'dhcp_failover_send_poolresp()' was in fact + sending POOLREQ messages instead of POOLRESP mesasges. This message + was essentially ignored since failover secondaries effectively do not + respond to POOLREQ messages. + +- Type definitions for various bitwidths of integers in the sunos5-5 + build of ISC DHCP have been fixed. It should compile and run more + easily when built in 64-bit for this platform. + +- "allow known-clients;" is now a legal syntax, to avoid confusion. + +- If one dhcp server chooses to 'load balance' a request to its failover + peer, it first checks to see if it believes said peer has a free + lease to allocate before ignoring the DISCOVER. + +- log() was logging a work buffer, rather than the value returned by + executing the statements configured by the user. In some cases, + the work buffer and the intended results were the same. In some other + cases, they were not. This was fixed thanks to a patch from Gunnar + Fjone and directconnect.no. + +- Compiler warnings for some string type conversions was fixed, thanks + to Andreas Gustafsson. + +- The netbsd build environments were simplified to one, in which + -Wconversion is not used, thanks to Andreas Gustafsson. + +- How randomness in the backoff-cutoff dhclient configuration variable + is implemented was better documented in the manpage, and the behaviour + of dhclient in REQUEST timeout handling was changed to match that of + DISCOVER timeout handling. + +- Omapi was hardened against clients that pass in null values, thanks + to a patch from Mark Jason Dominus. + +- A bug was fixed in dhclient that kept it from doing client-side + ddns updates. Thanks to a patch from Andreas Gustafsson, which + underwent some modification after review by Jason Vas Dias. + +- Failover implementations disconnected due to the network between + them (rather than one of the two shutting down) will now try to + re-establish the failover connection every 5 seconds, rather than + to simply try once and give up until one of them is restarted. + Thanks to a patch from Ulf Ekberg from Infoblox, and field testing + by Greger V. Teigre which led to an enhancement to it. + +- A problem that kept DHCP Failover secondaries from tearing down + ddns records was repaired. Thanks to a patch from Ulf Ekberg from + Infoblox. + +- 64bit pointer sizes are detected properly on FreeBSD now. + +- A bug was repaired where the DHCP server would leave stale references + to host records on leases it once thought about offering to certain + clients. The result would be to apply host and 'known' scopes to the + wrong clients (possibly denying booting). NOTE: The 'mis-host' patch + that was being circulated as a workaround is not the way this bug was + fixed. If you were a victim of this bug in 3.0.1, you are cautioned + to proceed carefully and see if it fixes your problem. + +- A bug was repaired in the server's DHCPINFORM handling, where it + tried to divine the client's address from the source packet and + would get it wrong. Thanks to Anshuman Singh Rawat. + +- A log message was introduced to help illuminate the case where the + server was unable to find a lease to assign to any BOOTP client. + Thanks to Daniel Baker. + +- A minor dhcpd.conf.5 manpage error was fixed. + + Changes since 3.0.1rc14 + +- The global variable 'cur_time' was centralized and is now uniformly of a + type #defined in system-dependent headers. It had previously been defined + in one of many places as a 32-bit value, and this causes mayhem on 64-bit + big endian systems. It probably wasn't too healthy on little endian + systems either. + +- A printf format string error introduced in rc14 was repaired. + +- AIX system-dependent header file was altered to only define NO_SNPRINTF + if the condition used to #ifdef in vsnprintf in AIX' header files + is false. + +- The Alpha/OSF system-dependent header file was altered to define + NO_SNPRINTF on OS revisions older than 4.0G. + +- omapip/test.c had string.h added to its includes. + + Changes since 3.0.1rc13 + +! CAN-2004-0460 - CERT VU#317350: Five stack overflow exploits were closed + in logging messages with excessively long hostnames provided by the + clients. It is highly probable that these could have been used by + attackers to gain arbitrary root access on systems using ISC DHCP 3.0.1 + release candidates 12 or 13. Special thanks to Gregory Duchemin for + both finding and solving the problem. + +! CAN-2004-0461 - CERT VU#654390: Once the above was closed, an opening + in log_*() functions was evidented, on some specific platforms where + vsnprintf() was not believed to be available and calls were wrapped to + sprintf() instead. Again, credit goes to Gregory Duchemin for finding + the problem. Calls to snprintf() are now linked to a distribution-local + snprintf implementation, only in those cases where the architecture is + not known to provide one (see includes/cf/[arch].h). If you experience + linking problems with snprintf/vsnprintf or 'isc_print_' functions, this + is where to look. This vulnerability did not exist in any previously + published version of ISC DHCP. + +- Compilation on hpux 11.11 was repaired. + +- 'The cross-compile bug fix' was backed out. + + Changes since 3.0.1rc12 + +- Fixed a bug in omapi lease lookup function, to form the hardware + address for the hash lookup correctly, thanks to a patch from + Richard Hirst. + +- Fixed a bug where dhcrelay was sending relayed responses back to the + broadcast address, but with the source's unicast mac address. Should + now conform to rfc2131 section 4.1. + +- Cross-compile bug fix; use $(AR) instead of ar. Thanks to Morten Brorup. + +- Fixed a crash bug in dhclient where dhcpd servers that do not provide + renewal times results in an FPE. As a side effect, dhclient can now + properly handle 0xFFFFFFFF (-1) expiry times supplied by servers. Thanks + to a patch from Burt Silverman. + +- The 'ping timeout' debugs from rc12 were removed to -DDEBUG only, + and reformatted to correct a compilation error on solaris platforms. + +- A patch was applied which fixes a case where leases read from the + leases database do not properly over-ride previously read leases. + +- dhcpctl.3 manpage was tweaked. + + Changes since 3.0.1rc11 + +- A patch from Steve Campbell was applied with minor modifications to + permit reverse dns PTR record updates with values containing spaces. + +- A patch from Florian Lohoff was applied with some modifications to + dhcrelay. It now discards packets whose hop count exceeds 10 by default, + and a command-line option (-c) can be used to set this threshold. + +- A failover bug relating to identifying peers by name length instead of + by name was fixed. + +- Delcaring failover configs within shared-network statements should no + longer result in error. + +- The -nw command line option to dhclient now works. + +- Thanks to a patch from Michael Richardson: + - Some problems with long option processing have been fixed. + - Some fixes to minires so that updates of KEY records will work. + +- contrib/ms2isc was updated by Shu-Min Chang of the Intel Corporation. + see contrib/ms2isc/readme.txt for revision notes. + +- Dhclient no longer uses shell commands to kill another instance of + itself, it sends the signal directly. Thanks to a patch from Martin + Blapp. + +- The FreeBSD dhclient-script was changed so that a failure to write to + /etc/resolv.conf does not prematurely end the script. This keeps dhclient + from looping infinitely when this is the case. Thanks to a patch from + Martin Blapp. + +- A patch from Bill Stephens was applied which resolves a problem with lease + expiry times in failover configurations. + +- A memory leak in configuration parsing was closed thanks to a patch from + Steve G. + +- The function which discovers interfaces will now skip non-broadcast or + point-to-point interfaces, thanks to a patch from David Brownlee. + +- Options not yet known by the dhcpd or dhclient have had their names + changed such that they do not contain # symbols, in case they should ever + appear in a lease file. An option that might have been named "#144" is + now "unknown-144". + +- Another patch from Bill Stephens which allows the ping-check timeout to + be configured as 'ping-timeout'. Defaults to 1. + + Changes since 3.0.1rc10 + +- Potential buffer overflows in minires repaired. + +- A change to the linux client script to use /bin/bash, since /bin/sh may + not be bash. + +- Some missing va_end cleanups thanks to a patch from Thomas Klausner. + +- A correction of boolean parsing syntax validation - some illegal syntaxes + that worked before are now detected and produce errs, some legal syntaxes + that errored before will now work properly. + +- Some search-and-replace errors that caused some options to change their + names was repaired. + +- Shu-min Chang of the Intel corporation has contributed a perl script and + module that converts the MS NT4 DHCP configuration to a ISC DHCP3 + configuration file. + +- Applied the remainder of the dhcpctl memory leak patch provided by Bill + Squier at ReefEdge, Inc. (groo@reefedge.com). + +- Missing non-optional failover peer configurations will now result in a soft + error rather than a null dereference. + + Changes since 3.0.1rc9 + +- A format string was corrected to fix compiler warnings. + +- A number of spelling corrections were made in the man pages. + +- The dhclient.conf.5 man page was changed to refer to do-forward-updates + rather than a configuration option that doesn't exist. + +- A FreeBSD-specific bug in the interface removal handling was fixed. + +- A Linux-specific Token Ring detection problem was fixed. + +- Hashes removed from as-yet-unknown agent options, having those options + appear in reality before we know about them will no longer produce + self-corrupting lease databases. + +- dhclient will use the proper port numbers now when using the -g option. + +- A order-of-operations bug with 2 match clauses in 1 class statement is + fixed thanks to a patch from Andrew Matheson. + +- Compilation problems on Solaris were fixed. + +- Compilation problems when built with DEBUG or DEBUG_PACKET were repaired. + +- A fix to the dhcp ack process which makes certain group options will be + included in the first DHCPOFFER message was made thanks to a patch from + Ling Gou. + +- A few memory leaks were repaired thanks to patches from Bill Squier at + ReefEdge, Inc. (groo@reefedge.com). + +- A fix for shared-networks that sometimes give clients options for the + wrong subnets (in particular, 'option routers') was applied, thanks to + Ted Lemon for the patch. + +- Omshell's handling of dotted octets as values was changed such that dots + one after the other produce zero values in the integer string. + + Changes since 3.0.1rc8 + +- Fix a format string vulnerability in the server that could lead to a + remote root compromise (discovered by NGSEC Research Team, www.ngsec.com). + +- Add additional support for NetBSD/sparc64. + +- Fix a bug in the command-line parsing of the client. Also, resolve + a memory leak. + +- Add better support for shells other than bash in the Linux client + script. + +- Various build fixes for modern versions of FreeBSD and Linux. + +- Fix a bad bounds check when printing binding state names. + +- Clarify documentation about fixed-address and multiple addresses. + +- Fix a typo in the authoritative error message. + +- Make a log entry when we can't write a billing class. + +- Use conversion targets that are the right size on all architectures. + +- Increment the hop count when relaying. + +- Log a message when lease state is changed through OMAPI. + +- Don't rerun the shared_network when evaluating the pool. + +- Fix a reversed test in the parser. + +- Change the type of rbuf_max. + +- Make FTS_LAST a manifest constant to quiet warnings. + + Changes since 3.0.1rc7 + +- Fix two compiler warnings that are generated when compiling on Solaris + with gcc. These stop the build, even though they weren't actually + errors, because we prefer that our builds generate no warnings. + + Changes since 3.0.1rc6 + +- Don't allow a lease that's in the EXPIRED, RELEASED or RESET state + to be renewed. + +- Implement lease stealing for cases where the primary has fewer leases + than the secondary, as called for by the standard. + +- Add a fudge factor to the lease expiry acceptance code, (suggested + by Kevin Miller of CMU). + +- Fix a bug in permit_list_match that made it much too willing to say + that two permit lists matched. + +- Unless DEBUG_DNS_UPDATES is defined, print more user-friendly (and + also more compact) messages about DNS updates. + +- Fix a bug in generating wire-format domain names for the FQDN option. + +- Fix a bug where the FQDN option would not be returned if the client + requested it, contrary to the standard. + +- On Darwin, use the FreeBSD DHCP client script. + +- On NetBSD/sparc, don't check for casting warnings. + +- Add a flag in the DHCP client to disable updating the client's A + record when sending an FQDN option indicating that the client is + going to update its A record. + +- In the client, don't attempt a DNS update until one second after + configuring the new IP address, and if the update times out, keep + trying until a response, positive or negative, is received from the + DNS server. + +- Fix an uninitialized memory bug in the DHCP client. + +- Apply some FreeBSD-specific bug fixes suggested by Murray Stokely. + +- Fix a bug in ns_parserr(), where it was returning the wrong sort + of result code in some cases (suggested by Ben Harris of the + NetBSD project). + +- Fix a bug in is_identifier(), where it was checking against EOF + instead of the END_OF_FILE token (also suggested by Ben Harris). + +- Fix a bug where if an option universe contained no options, the + DHCP server could dump core (Walter Steiner). + +- Fix a bug in the handling of encapsulated options. + +- Fix a bug that prevented NWIP suboptions from being processed. + +- Delete the FTS_BOOTP and FTS_RESERVED states and implement them + as modifier flags to the FTS_ACTIVE state, as called for in the + failover protocol standard. + +- Fix bugs in the pool merging code that resulted in references and + dereferences of null pointers. This bug had no impact unless the + POINTER_DEBUG flag was defined. + +- In the server, added a do-forward-updates flag that can be used to + disable forward updates in all cases, so that sites that want the + clients to take sole responsibility for updating their A record can + do so. + +- Make it possible to disable optimization of PTR record updates. + + Changes since 3.0.1rc5 + +- Include some new documentation and changes provided by Karl Auer. + +- Add a workaround for some Lexmark printers that send a double-NUL- + terminated host-name option, which would break DNS updates. + +- Fix an off-by-one error in the MAC-address checking code for + DHCPRELEASE that was added in 3.0.1rc5. + +- Fix a bug where client-specific information was not being discarded + from the lease when it expired or was released, resulting in + problems if the lease was reallocated to a different client. + +- If more than one allocation pool is specified that has the same set + of constraints as another allocation pool on the same shared + network, merge the two pools. + +- Don't print an error in fallback_discard, since this just causes + confusion and does not appear to be helping to encourage anyone to + fix this bug. + + Changes since 3.0.1rc4 + +- Fix a bug that would cause the DHCP server to spin if asked to parse + a certain kind of incorrect statement. + +- Fix a related bug that would prevent an error from being reported in + the same case. + +- Additional documentation. + +- Make sure that the hardware address matches the lease when + processing a DHCPRELEASE message. + + Changes since 3.0.1rc3 + +- A minor bug fix in the arguments to a logging function call. +- Documentation update for dhcpd.conf. + + Changes since 3.0.1rc2 + +- Allow the primary to send a POOLREQ message. This isn't what the current + failover draft says to do, so we may have to back it out if I can't get the + authors to relent, but the scheme for balancing that's specified in the + current draft seems needlessly hairy, so I'm floating a trial balloon. + The rc1 code did not implement the method described in the draft either. + + Changes since 3.0.1rc1 + +- Treat NXDOMAIN and NXRRSET as success when we are trying to delete a + domain or RRSET. This allows the DHCP server to forget about a name + it added to the DNS once it's been removed, even if the DHCP server + wasn't the one that removed it. + +- Install defaults for failover maximum outstanding updates and maximum + silent time. This prevents problems that might occur if these values + were not configured. + +- Don't do DDNS deletes if ddns-update-style is none. + +- Return relay agent information options in DHCPNAK. This prevents DHCPNAK + messages from being dropped when the relay agent information option contains + routing information. + +- Fix a problem where coming up in recover wouldn't result in an update + request being sent. + +- Add some more chatty messages when we start a recovery update and when it's + done. + +- Fix a possible problem where some state might have been left around + after the peer lost contact and regained contact about how many updates + were pending. + +- Don't nix a lease update because of a lease conflict. This test has + never (as far as I know) prevented a mistake, and it appears to cause + problems with failover. + +- Add support in rc history code for keeping a selective history, rather + than a history of all references and dereferences. This code is only used + when extensive additional debugging is enabled. + + Changes since 3.0 + +- Make allocators for hash tables. As a side effect, this fixes a memory + smash in the subclass allocation code. + +- Fix a small bug in omshell where if you try to close an object when + no object is open, it dumps core. + +- Fix an obscure coredump that could occur on shutdown. + +- Fix a bug in the recording of host declaration rubouts in the lease file. + +- Fix two potential spins in the host deletion code. + +- Fix a core dump that would happen if an application tried to update + a host object attribute with a null value. + + Changes since 3.0 Release Candidate 12 + +- Fix a memory leak in the evaluation code. + +- Fix an obscure core dump. + +- Print a couple of new warnings when parsing the configuration file + when crucial information is left out. + +- Log "no free leases" as an error. + +- Documentation updates. + + Changes since 3.0 Release Candidate 11 + +- Always return a subnet selection option if one is sent. + +- Fix a warning that was being printed because an automatic data + structure wasn't zeroed. + +- Fix some failover state transitions that were being handled + incorrectly. + +- When supersede_lease is called on a lease whose end time has already + expired, but for which a state transition has not yet been done, do + a state transition. This fixes the case where if the secondary + allocated a lease to a client and the lease "expired" while the + secondary was in partner-down, no expiry event would actually + happen, so the lease would remain active until the primary was + restarted. + + Changes since 3.0 Release Candidate 10 + +- Fix a bug that was preventing released leases from changing state + in failover-enabled pools. + +- Fix a core dump in the client identifier finder code (for host + declarations). + +- Finish fixing a bug where bogus data would sometimes get logged to + the dhclient.leases file because it was opened as descriptor 2. + +- Fix the Linux dhclient-script according to suggestions made by + several people on the dhcp-client mailing list. + +- Log successful DNS updates at LOG_INFO, not LOG_ERROR. + +- Print an error message and refuse to run if a failover peer is + defined but not referenced by any pools. + +- Correct a confusing error message in failover. + Changes since 3.0 Release Candidate 9 - Fix a bug in lease allocation for Dynamic BOOTP clients. @@ -208,10 +886,10 @@ and for prodding me into improving it. - Clean up the memory allocation/reference history printer. -- Support input of dotted quads and colon-seperated hex lists as +- Support input of dotted quads and colon-separated hex lists as attribute values in omshell. -- Fix a typo in the linux interface discovery code. +- Fix a typo in the Linux interface discovery code. - Conditionalize a piece of trace code that wasn't conditional. @@ -245,7 +923,7 @@ and for prodding me into improving it. - Fix compile problem on SunOS 4.x -- If a signature algorithm is not termined with '.', terminate it so +- If a signature algorithm is not terminated with '.', terminate it so that comparisons between fully-qualified names will work consistently. @@ -279,7 +957,7 @@ and for prodding me into improving it. - Change the conditions under which a DHCPRELEASE is actually committed to be consistent with lease binding states rather than - using the lease end time. THis may fix some problems with the + using the lease end time. This may fix some problems with the billing class code. - Fix a bug where lease updates would fail on Digital Unix (and maybe @@ -458,7 +1136,7 @@ and for prodding me into improving it. given a lease where the hardware address was correct but the client identifier was not, resulting in a lease conflict message. -- Fix a problem where the server could write out a colon-seperated +- Fix a problem where the server could write out a colon-separated hex list as a value for a variable, which would then not parse. The fix is to always write strings as quoted strings, with any non-printable characters quoted as octal escape sequences. So |