[#221] README and RELNOTES updated (dhclient,dhcrelay reached EOL)

README

@@ -1,6 +1,6 @@
 	      Internet Systems Consortium DHCP Distribution
-			     Version 4.4.2
+			     Version 4.4.3
-			    22 January 2020
+			    26 January 2022
 
 			      README FILE
 
@@ -62,13 +62,15 @@ documented in the dhclient-script man page.   The format of the DHCP
 client lease database is documented in the dhclient.leases man page.
 The source for all these man pages is in the client/ subdirectory in
 the distribution.   In addition, the dhcp-options man page should be
-referred to for information about DHCP options.
+referred to for information about DHCP options. The client component
+is reaching End-of-Life and will not be part of future releases.
 
 DHCP relay agent documentation is in the dhcrelay man page, the source
-for which is distributed in the relay/ subdirectory.
+for which is distributed in the relay/ subdirectory. The relay component
+is reaching End-of-Life and will not be part of future releases.
 
 KEA Migration Assistant documentation, including how to build, install
-and use it, is including in the keama directory.
+and use it, is including in the keama/ directory.
 
 To read installed manual pages, use the man command.  Type "man page"
 where page is the name of the manual page.   This will only work if
@@ -97,12 +99,12 @@ directory, it may not have up-to-date information).
 To build the DHCP Distribution, unpack the compressed tar file using
 the tar utility and the gzip command - type something like:
 
-	gunzip dhcp-4.4.2.tar.gz
+	gunzip dhcp-4.4.3.tar.gz
-	tar xvf dhcp-4.4.2.tar
+	tar xvf dhcp-4.4.3.tar
 
 			    CONFIGURING IT
 
-Now, cd to the dhcp-4.4.2 subdirectory that you've just created and
+Now, cd to the dhcp-4.4.3 subdirectory that you've just created and
 configure the source tree by typing:
 
 	./configure
@@ -348,7 +350,7 @@ more information, consult the vconfig man pages.
 			       ATF
 
 Please see the file DHCP/doc/devel/atf.dox for a description of building
-and using these tools.  
+and using these tools.
 
 The optional unit tests use ATF (Automated Testing Framework) including
 the atf-run and atf-report tools. ATF deprecated these tools in
@@ -384,7 +386,7 @@ the dhcp-users or dhcp-announce mailing lists.
 WHERE TO SEND FEATURE REQUESTS: We like to hear your feedback.  We may
 not respond to it all the time, but we do read it.  If ISC DHCP doesn't
 work well for you, or you have an idea that would improve it for your
-use, please create an issue at https://gitlab.isc.org/isc-projects/dhcp/issues.  
+use, please create an issue at https://gitlab.isc.org/isc-projects/dhcp/issues.
 This is also an excellent place to send patches that add new features.
 
 WHERE TO REPORT BUGS: If you want the act of sending in a bug report
@@ -393,17 +395,20 @@ software, you are asking for help.  Your bug report is helpful to us,
 but fundamentally you are making a support request, so please use the
 addresses described in the previous paragraphs.  If you are _sure_ that
 your problem is a bug, and not user error, or if your bug report
-includes a patch, you can submit it to our ticketing system at 
+includes a patch, you can submit it to our ticketing system at
-https://gitlab.isc.org/isc-projects/dhcp/issues.  If you have not received 
+https://gitlab.isc.org/isc-projects/dhcp/issues.  If you have not received
 a notice that the ticket has been resolved, then we're still working on it.
+Notice that this is the final release that features client and relay
+components. Reporting bugs in them makes limited sense. The ISC team
+will not be fixing any issues related to client or relay. They may be
+useful for other users to document some problems or perhaps discuss
+and share workarounds.
 
 PLEASE DO NOT REPORT BUGS IN OLD SOFTWARE RELEASES!  Fetch the latest
 release and see if the bug is still in that version of the software,
-and if it is still present, _then_ report it.  ISC release versions 
+and if it is still present, _then_ report it.  ISC release versions
-always have three numbers, for example: 1.2.3.  The 'major release' is 
+always have three numbers, for example: 1.2.3.  The 'major release' is
-1 here, the 'minor release' is 2, and the 'maintenance release' is 3.  
+1 here, the 'minor release' is 2, and the 'maintenance release' is 3.
-ISC will accept bug reports against the most recent two major.minor
-releases: for example, 1.0.0 and 0.9.0, but not 0.8.* or prior.
 
 PLEASE take a moment to determine where the ISC DHCP distribution
 that you're using came from.  ISC DHCP is sometimes heavily modified
@@ -483,7 +488,8 @@ agent. DHCP 3 was released in October 2001 and included DHCP failover
 support, OMAPI, Dynamic DNS, conditional behaviour, client classing,
 and more. Version 3 of the DHCP server was funded by Nominum, Inc.
 The 4.0 release in December 2007 introduced DHCPv6 protocol support
-for the server and client.
+for the server and client. The client and relay components reached
+their End-of-Life in January 2022.
 
 This product includes cryptographic software written
 by Eric Young (eay@cryptsoft.com).

RELNOTES

@@ -1,6 +1,6 @@
                 Internet Systems Consortium DHCP Distribution
-                            Version 4.4.2
+                            Version 4.4.3
-                            22 January 2020
+                            26 January 2022
                              Release Notes
 
                               NEW FEATURES
@@ -9,84 +9,35 @@ Please note that that ISC DHCP is now licensed under the Mozilla Public License,
 MPL 2.0. Please see https://www.mozilla.org/en-US/MPL/2.0/ to read the MPL 2.0
 license terms.
 
-While release 4.4.2 is primarily a maintenance release that addresses a number
+NOTE: The client and relay components are reaching their End-Of-Life cycle.
-of defects, it does introduce a few new features:
+4.4.3 is the final release that features them.
 
-- Keama - Keama is a migration utility that assists in converting ISC DHCP
+While release 4.4.3 is primarily a maintenance release that addresses a number
-  server configuration files to Kea configuration files.  It is found in the
+of issues, it does introduce a few of small new features:
-  keama subdirectory and includes a README.md file with instructions on how
-  to build it as well as a manpage on its usage.
 
-- Two new server parameters related to ping checking were added:
+1. BIND libraries updated to the latest 9.11.36. This fixes a number of compilation
+  issues on various systems, including OpenWRT.
+   [gitlab #218, #171, #180, #192]
 
-1. ping-cltt-secs which allows the user to specify the number of seconds
+2. Improve PRNG initialization. There is now a new configure flag --with-randomdev=PATH
-   that must elapse since CLTT before a ping check is conducted.
+  that specifies the device to read the initial seed from. That is typically
+  /dev/random (the default value) or /dev/urandom, but may be other as preferred on
+  your system. If this option is enabled, dhclient will use the file as a seed. If
+  not, the earlier algorithm (get last 4 bytes of hardware addresses from all network
+  interfaces that have them, use current time and process ID).
 
-2. ping-timeout-ms which allows the user to specify the amount of time the
+3. The IPv6-only preferred option, defined in RFC8925, is now supported.
-   server waits for a ping-check response in milliseconds rather than in
+   [gitlab #132]
-   seconds.
 
-In general, the areas of focus for ISC DHCP 4.4 were:
+4. Compilation fixed for gcc-10.
+   [gitlab #117]
 
-1. Dynamic DNS additions
+5. Client fix: wrong argument to memcpy()
-2. dhclient improvements
+   [gitlab #190]
-3. Support for dynamic shared libraries
 
-Dynamic DNS Improvements:
+6. The server's limit on the size of lease file that can be loaded at start up
-
+   is now only enforced on 32-bit systems.
-- We added three new server configuration parameters which influence DDNS
+   [gitlab #64]
-  conflict resolution:
-
-    1. ddns-dual-stack-mixed-mode - alters DNS conflict resolution behavior
-    to mitigate issues with non-compliant clients in dual stack environments.
-
-    2. ddns-guard-id-must-match - relaxes the DHCID RR client id matching
-    requirement of DNS conflict resolution.
-
-    3. ddns-other-guard-is-dynamic - alters dual-stack-mixed-mode behavior to
-    allow unguarded DNS entries to be overwritten in certain cases
-
-- The server now honors update-static-leases parameter for static DHCPv6
-  hosts.
-
-dhclient Improvements:
-
-  - We've added three command line parameters to dhclient:
-
-    1. --prefix-len-hint - directs dhclient to use the given length as
-    the prefix length hint when requesting prefixes
-
-    2. --decline-wait-time - instructs the client to wait the given number
-    of seconds after declining an IPv4 address before issuing a discover
-
-    3. --address-prefix-len - specifies the prefix length passed by dhclient
-    into the client script (via the environment variable ip6_prefixlen) with
-    each IPv6 address.  We added this parameter because we have changed the
-    default value from 64 to 128 in order to be compliant with RFC3315bis
-    draft (-09, page 64) and RFC5942, Section 4, point 1.
-    **WARNING**: The new default value of 128 may not be backwardly compatible
-    with your environment. If you are operating without a router, such as
-    between VMs on a host, you may find they cannot see each other with prefix
-    length of 128. In such cases, you'll need to either provide routing or use
-    the command line parameter to set the value to 64. Alternatively you may
-    change the default at compile time by setting DHCLIENT_DEFAULT_PREFIX_LEN
-    in includes/site.h.
-
-  - dhclient will now generate a DHCPv6 DECLINE message when the client script
-    indicates a DAD failure
-
-Dynamic shared library support:
-
-  Configure script, configure.ac+lt, which supports libtool is now provided
-  with the source tar ball.  This script can be used to configure ISC DHCP
-  to build with libtool and thus use dynamic shared libraries.
-
-Other Highlights:
-
- - The server now supports dhcp-cache-threshold for DHCPv6 operations
- - The server now supports DHPv6 address allocation based on EUI-64 DUIDs
- - Experimental support for alternate relay port in the both the server
-   and relay for IPv4, IPv6 and 4o6 (see: draft-ietf-dhc-relay-port-10.txt)
 
 For information on how to install, configure and run this software, as
 well as how to find documentation and report bugs, please consult the