[prev in list] [next in list] [prev in thread] [next in thread]
List: dhcp-announce
Subject: 4.1-ESV-R13b1 is now available
From: Shawn Routhier <sar () isc ! org>
Date: 2016-03-09 22:35:45
Message-ID: B8FD1A92-757D-4150-8C9C-8008B6C59D6A () isc ! org
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
ISC DHCP 4.1-ESV-R13b1 is now available for download.
This is the release of ISC DHCP 4.1-ESV-R13b1, a maintenance
release which contains a number of bug fixes and two fixes
for previously released security issues.
Field testing is an important part of our quality process.
Please report bugs to dhcp-bugs@isc.org.
A list of the changes in this release has been appended to the end
of this message. For a complete list of changes from any previous
release, please consult the RELNOTES file within the source distribution.
They can also be found at:
https://kb.isc.org/article/AA-01358/82/DHCP-4.1-ESV-R13b1-Release-Notes.html
Knowledge base articles about various features can be found starting from:
https://kb.isc.org/category/201/0/10/Software-Products/DHCP/Features/
Webinars can be found here:
http://www.youtube.com/user/ISCdotorg
This release, and its OpenPGP-signatures are available now from:
https://www.isc.org/downloads/DHCP/
ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz
ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha512.asc
ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha256.asc
ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha1.asc
ISC's Release Signing Key can be obtained at:
http://www.isc.org/about/openpgp/
The following are changes that may be more interesting and require
a bit more explanation.
We have changed the default set-up for choosing a program name for
use in logging. Previously we used a hardcoded name for the client,
relay and server. We have changed to using the base name of the program.
This is intended to help differentiate syslog entries when using both v4
& v6 clients or servers. We don't expect anybody to need the old style
but if you do it is available via modifying includes/site.h
and defining OLD_LOG_NAME. [ISC-Bugs #38692]
We have added a new parameter, authoring-byte-order, to the lease file.
This value is used to allow a lease file written in one byte order
to be read on a machine with a different byte order. If you have
a program to process a lease file you may need to update it to
handle this string. [ISC-Bugs #38396]
The IETF determined that there were problems with the processing
required for IA_NAs (RFC3315) and IA_PDs (RFC3633). The issues
are described in RFC7550. As part of updating the client code to
the new RFC we also re-arranged how it chooses between different
servers by changing the weights used when socring an advertise.
The new weighting will prefer more bindings (IAs) over more addresses
within a binding. As most users will get a single address in
as single binding and only get an advertise from a single server
there won't be any difference. If you do need the old weighting
for some reason you can edit includes/site.h and define
USE_ORIGINAL_CLIENT_LEASE_WEIGHTS. [ISC-Bugs #40190]
We have modified the error reporting in the client, relay and server
to better indicate which command line option caused an error. As
we don't exepct this to be an issue we have made it the default.
If you you need the old error messages you can edit includes/site.h
and undefine PRINT_SPECIFIC_CL_ERRORS. [ISC-Bugs #40321]
As mentioned in the recent security annoucement we found an issue
with our handling of exccessive numbers of connections. While we
beleive the best idea is for people to properly secure their DHCP
severs (disable OMAPI if not in use, use firewalls to limit access
to OMAPI and failove ports and use process limits to restrict the
resources the servers can use) we have added code to limit the number
of connections a server will allow. We have chosen 200 as the
default number which should be large enough for most configurations.
You may adjust this value by editing includes/site.h and changing
the value of MAX_FD_VALUE. A value of 0 means unlimited. We will
be evaluating the connection code in more detail in the future and
may change how this works. [ISC-Bugs #41845]
The following is the list of all changes for this release.
Changes since 4.1-ESV-R12
- Corrected a static analyzer warning in common/execute.c
[ISC-Bugs #40374]
- ISC DHCP now follows the common convention to use the base name a
program is invoked with (aka argv[0], vs. a builtin name) for
logs. This should help differentiate syslog entires for DHCPv4 and
DHCPv6 servers. You can define OLD_LOG_NAME in includes/site.h to
keep the previous behavior.
[ISC-Bugs #38692]
- The linux packet filter code now correctly treats only the least significant
12 bits in an inbound packet's TCI value as the VLAN id (per IEEE 802.1Q).
Prior to this it was using the entire 16 bit value as the VLAN id and
incorrectly discarding packets. Thanks to Jiri Popelka at Red Hat for
reporting this issue and supplying its patch.
[ISC-Bugs #40591]
- Fixed several static analysis issues such as potential null
references, unchecked strdup returns. Thanks to Bill Parker (wp02855 at
gmail dot com) who identified these issues and supplied patches to
address them.
[ISC-Bugs #40754]
[ISC-Bugs #40823]
- Corrected compilation errors that prohibited building the server's
ATF unit tests when failover is disabled.
[ISC-Bugs #40372]
- Added dhcpv6 and delayed-ack to settings listed in the "Features:"
section of the configure script output. Additionally, all of the
features reported on will now always show either a "yes" or "no"
value. Prior to this features left to their default setting would
not show a value.
[ISC-Bugs #40381]
- Added a parameter, authoring-byte-order, to the lease file. This value
is automatically added to the top of new lease files by the server and
indicates the internal byte order (big endian or little endian) of the
server. This permits lease files generated on a server with one form of
byte order to be used on a server with the opposite form.
[ISC-Bugs #38396]
- Fix a small memory leak in the DHCPv6 version of the client code.
This is unlikely to cause significant issues in actual use.
[ISC-Bugs #40990]
- Corrected a few minor memory leaks in omapi's dereferencing of
host objects. Thanks to Jiri Popelka at Red Hat for reporting
the issue and supplying the patches.
[ISC-Bugs #33990]
- Update the client code to better support getting IA_NAs and IA_PDs
in the same packet, see RFC7550 for some discussion.
[ISC-Bugs #40190]
! Update the bounds checking when receiving a packet.
Thanks to Sebastian Poehn from Sophos for the bug report and a suggested
patch.
[ISC-Bugs #41267]
CVE: CVE-2015-8605
- When handling an incorrect command line for dhcpd, dhclient or dhcrelay
print out a specific error message about the first error in addition
to the usage string. This may be disabled by editing includes/site.h.
[ISC-Bugs #40321]
[ISC-Bugs #41454]
- The configure script will now exit with an error message if it cannot find
pkg-config (needed to locate ATF used for building unit tests). Prior to
this the script would exit indicating success causing subsequent attempts
to build the software to fail.
[ISC-Bugs #40371]
- Properly terminate strings before passing them to regex and fix
a boundary error when creating certain new data strings.
Thanks to Andrey Jr. Melnikov for the bug report.
[ISC-Bugs #41217]
- Option expressions, such as prepend and append, are now supported when
running dhclient for IPv6. Prior to this such statements in the
client configuration file would be parsed but have no affect. Thanks
to Jiri Popelka at Red Hat for reporting the issue.
[ISC-Bugs #39952]
- A failover primary server will now accept a binding status update from the
secondary which transitions a lease from ACTIVE to ABANDONED. This accounts
for instances in which a client declines a lease and only the secondary
server receives it. Prior to this the primary server would reject such an
update as an "invalid state transition".
[ISC_BUGS #25189]
- Properly allocate memory for a bpf filter.
Thanks to Bill Parker (wp02855 at gmail dot com) who identified this issue.
[ISC-Bugs #41485]
- The DHCPv6 server now handles long valid and preferred lease times better.
Values that would cause the internal end time of the lease to wrap are
modified to work as infinite.
[ISC-Bugs #40773]
- Correct outputting of long lines in the lease file when writing
a lease that includes long strings in an execute statement.
[ISC-Bugs #40994]
- The server will now correctly treat a lease as reserved when the client
requests an infinite lease time (i.e. OxFFFFFFFF) and "infinite-is-reserved"
is enabled. Prior to this the server would halt. In addition, corrections
were made to the server to allow a lease's flags field to be set via omapi.
Prior to this, the server, depending on the host architecture, would
incorrectly parse the new flags value from the omapi message.
[ISC-Bugs #31179]
- Add a new global DHCPv6 option, dhcpv6-set-tee-times, which when enabled
instructs the server to calculate T1 and T2 as recommended in RFC 3315,
Section 22.4.
[ISC-Bugs #25687]
- Corrected minor Coverity issues.
[ISC-Bugs #35144]
- Corrected interface name formation when using DLPI under Solaris 11. As of
Solaris 11, ethernet device files are located in "/dev/net". The configure
script has been modified to detect this situation and adjust the directory
used accordingly. Thanks to Jarkko Torppa for reporting this issue and
submitting a patch.
[ISC-Bugs #37954]
[ISC-Bugs #40752]
- Add a dereference call when handling an error condition while
decoding a packet and clean up some memory on error conditions.
[ISC-Bugs #41774]
! Add an option in site.h to limit the number of failover and control
connections the server will accept. By default this is 200.
[ISC-Bugs #41845]
[Attachment #5 (unknown)]
<html><head><meta http-equiv="Content-Type" content="text/html \
charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; -webkit-line-break: after-white-space;" class=""><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">ISC DHCP 4.1-ESV-R13b1 is now \
available for download.</div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo; min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">This is the release of ISC DHCP \
4.1-ESV-R13b1, a maintenance</div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class="">release which contains a number of bug fixes and two \
fixes</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">for previously released security issues.</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">Field testing is an important part of our quality process.</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">Please report bugs \
to <a href="mailto:dhcp-bugs@isc.org" class="">dhcp-bugs@isc.org</a>.</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class="">A list of the changes in this release has been appended to the \
end</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">of \
this message. For a complete list of changes from any previous</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">release, please \
consult the RELNOTES file within the source distribution.</div><div style="margin: \
0px; font-size: 11px; font-family: Menlo;" class="">They can also be found \
at:</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: \
13px;" class=""><br class=""></div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class=""> <a \
href="https://kb.isc.org/article/AA-01358/82/DHCP-4.1-ESV-R13b1-Release-Notes.html" \
class="">https://kb.isc.org/article/AA-01358/82/DHCP-4.1-ESV-R13b1-Release-Notes.html</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class="">Knowledge base articles about various features can be found starting \
from:</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: \
13px;" class=""><br class=""></div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class=""> <a \
href="https://kb.isc.org/category/201/0/10/Software-Products/DHCP/Features/" \
class="">https://kb.isc.org/category/201/0/10/Software-Products/DHCP/Features/</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class="">Webinars can be found here:</div><div style="margin: 0px; font-size: \
11px; font-family: Menlo; min-height: 13px;" class=""><br class=""></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> <a \
href="http://www.youtube.com/user/ISCdotorg" \
class="">http://www.youtube.com/user/ISCdotorg</a></div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">This release, and its OpenPGP-signatures are available now from:</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class=""> <a href="https://www.isc.org/downloads/DHCP/" \
class="">https://www.isc.org/downloads/DHCP/</a></div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> <a \
href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz" \
class="">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> <a \
href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha512.asc" \
class="">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha512.asc</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> <a \
href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha256.asc" \
class="">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha256.asc</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> <a \
href="ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha1.asc" \
class="">ftp://ftp.isc.org/isc/dhcp/4.1-ESV-R13b1/dhcp-4.1-ESV-R13b1.tar.gz.sha1.asc</a></div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class="">ISC's Release Signing Key can be obtained at:</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class=""> <a href="http://www.isc.org/about/openpgp/" \
class="">http://www.isc.org/about/openpgp/</a></div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">The following are changes that may be more interesting and require</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">a bit more \
explanation.</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">We have changed the default set-up for choosing a \
program name for</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">use in logging. Previously we used a hardcoded name for the \
client,</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">relay and server. We have changed to using the base name of the \
program.</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">This is intended to help differentiate syslog entries when using both \
v4</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">& \
v6 clients or servers. We don't expect anybody to need the old style</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">but if you do it \
is available via modifying includes/site.h </div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">and defining OLD_LOG_NAME. \
[ISC-Bugs #38692]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">We have added a new parameter, \
authoring-byte-order, to the lease file.</div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">This value is used to allow a lease file written \
in one byte order</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">to be read on a machine with a different byte order. If you \
have</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">a \
program to process a lease file you may need to update it to</div><div style="margin: \
0px; font-size: 11px; font-family: Menlo;" class="">handle this string. \
[ISC-Bugs #38396]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">The IETF determined that there were problems with \
the processing</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">required for IA_NAs (RFC3315) and IA_PDs (RFC3633). The \
issues</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">are described in RFC7550. As part of updating the client code \
to</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">the \
new RFC we also re-arranged how it chooses between different</div><div style="margin: \
0px; font-size: 11px; font-family: Menlo;" class="">servers by changing the weights \
used when socring an advertise.</div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class="">The new weighting will prefer more bindings (IAs) over \
more addresses</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">within a binding. As most users will get a single address in</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">as single binding \
and only get an advertise from a single server</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">there won't be any difference. \
If you do need the old weighting</div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class="">for some reason you can edit includes/site.h and \
define</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">USE_ORIGINAL_CLIENT_LEASE_WEIGHTS. [ISC-Bugs #40190]</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class="">We have modified the error reporting in the client, relay and \
server</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">to better indicate which command line option caused an error. \
As</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">we \
don't exepct this to be an issue we have made it the default.</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">If you you need \
the old error messages you can edit includes/site.h</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">and undefine PRINT_SPECIFIC_CL_ERRORS. \
[ISC-Bugs #40321]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">As mentioned in the recent security annoucement \
we found an issue</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">with our handling of exccessive numbers of connections. While \
we</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">beleive the best idea is for people to properly secure their DHCP</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">severs (disable \
OMAPI if not in use, use firewalls to limit access</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">to OMAPI and failove ports and use \
process limits to restrict the</div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class="">resources the servers can use) we have added code to \
limit the number</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">of connections a server will allow. We have chosen 200 as \
the</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">default number which should be large enough for most \
configurations.</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">You may adjust this value by editing includes/site.h and changing</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">the value of \
MAX_FD_VALUE. A value of 0 means unlimited. We will</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class="">be evaluating the \
connection code in more detail in the future and</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class="">may change how this works. \
[ISC-Bugs #41845]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">The following is the list of all changes for this \
release.</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class=""> \
Changes since 4.1-ESV-R12</div><div style="margin: \
0px; font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">- Corrected a static analyzer warning in common/execute.c</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> [ISC-Bugs \
#40374]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">- ISC DHCP now follows the common convention to \
use the base name a</div><div style="margin: 0px; font-size: 11px; font-family: \
Menlo;" class=""> program is invoked with (aka argv[0], vs. a builtin name) \
for</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> logs. This should help differentiate syslog entires for DHCPv4 \
and</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> DHCPv6 servers. You can define OLD_LOG_NAME in includes/site.h \
to</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> keep the previous behavior.</div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class=""> [ISC-Bugs #38692]</div><div style="margin: \
0px; font-size: 11px; font-family: Menlo; min-height: 13px;" class=""><br \
class=""></div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class="">- The linux packet filter code now correctly treats only the least \
significant</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> 12 bits in an inbound packet's TCI value as the VLAN id (per IEEE \
802.1Q).</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> Prior to this it was using the entire 16 bit value as the VLAN id \
and</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> incorrectly discarding packets. Thanks to Jiri Popelka at Red \
Hat for</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> reporting this issue and supplying its patch.</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo;" class=""> [ISC-Bugs \
#40591]</div><div style="margin: 0px; font-size: 11px; font-family: Menlo; \
min-height: 13px;" class=""><br class=""></div><div style="margin: 0px; font-size: \
11px; font-family: Menlo;" class="">- Fixed several static analysis issues such as \
potential null</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> references, unchecked strdup returns. Thanks to Bill Parker \
(wp02855 at</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> gmail dot com) who identified these issues and supplied patches \
to</div><div style="margin: 0px; font-size: 11px; font-family: Menlo;" \
class=""> address them.</div><div style="margin: 0px; font-size: 11px; \
font-family: Menlo;" class=""> [ISC-Bugs #40754]</div><div style="margin: 0px; \
font-size: 11px; font-family: Menlo;" class=""> [ISC-Bugs #40823]</div><div \
style="margin: 0px; font-size: 11px; font-family: Menlo; min-height: 13px;" \
class=""><br class=""></div><div style="margin: 0px; font-size: 11px; font-family: \
_______________________________________________
dhcp-announce mailing list
dhcp-announce@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-announce
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic