Opened 9 years ago
Closed 9 years ago
#5874 closed enhancement (fixed)
dhcpcd-6.6.4
Reported by: | Fernando de Oliveira | Owned by: | Fernando de Oliveira |
---|---|---|---|
Priority: | normal | Milestone: | 7.7 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
http://roy.marples.name/downloads/dhcpcd/dhcpcd-6.6.4.tar.bz2
http://roy.marples.name/archives/dhcpcd-discuss/2014/0906.html
dhcpcd-6.6.3 has been released with the following changes: * Log which IP address we are ARPing. * Only free other ARP states if not assinging an IPv4LL address. * Reload global config when running per interface commands. This matches the signal behaviour. * If we don't have a hardware address, fallback to creating a default IAID from the interface name and index as we used to. * Loopback interfaces have routes scoped to the host only. * If we don't have a hwlen and no clientid has been set, force a DUID based ClientID. * Disable IPv6RS if a loopback, pointopoint or not a multicast interface. * If allowinterfaces is not specified, allow all configured interfaces to work, such as loopback and ppp. * When not daemonising, don't exit on timeout. * Zero length UDP packets are not an error condition on the socket. Thanks to Michał Kępień. * If the IP address is still on the interface when reading a lease, fake add the address and routes so the lease can be cleaned up if needed. From dhcpcd-6.3.3 to 6.6.2, dhcpcd was vulnerable to a zero length UDP packet which would cause the socket to close resulting in a DoS. For IPv4 sockets, triggering a carrier reset would be enough to re-open the socket. For IPv6 sockets, dhcpcd would have to be restarted.
http://roy.marples.name/archives/dhcpcd-discuss/2014/0907.html
dhcpcd-6.6.4 has been released with the following changes: * Fix a compile warning in dhcpcd-6.6.3 * Notify dhcpcd-run-hooks if running in debug mode * Report selected profile in test mode
Change History (2)
comment:1 by , 9 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
Fixed at r15023.