Simon Kelley 03fd0c19ef Clear down SLAAC-name data when a DHCP lease loses its hostname. ...

If a DHCPv4 lease loses its hostname, then the DHCPv6 name-address mapping
derived from it become invalid and need to be cleared.

Similarly, when a hostname is added to an existing lease, new
SLAAC-name data needs to be generated.

Thanks Martin Vlach (and Claude) for finding a symptom of this in
the SLAAC logging code. This patch fixes that and does the correct
thing more generally.

2026-10-01 20:43:10 +01:00

bld

…

contrib

Fix OOB writes in contrib/leasequesry/leasequery.c

2026-05-30 15:58:52 +01:00

dbus

…

logo

…

man

Add man page warning about untrusted data in the environment of DHCP-script.

2026-08-15 15:59:57 +01:00

po

…

src

Clear down SLAAC-name data when a DHCP lease loses its hostname.

2026-10-01 20:43:10 +01:00

submodules

…

.gitattributes

…

.gitignore

…

.gitmodules

…

Android.mk

…

CHANGELOG

Fix heap OOB read in zone_status()

2026-10-01 15:34:53 +01:00

CHANGELOG.archive

…

COPYING

…

COPYING-v3

…

debian

…

dnsmasq.conf.example

…

doc.html

…

FAQ

…

Makefile

Bump copyrights to 2026.

2026-04-08 12:08:18 +01:00

setup.html

…

trust-anchors.conf

…

VERSION

…

S

Description

No description provided

12 MiB

Languages

C 94.3%

Perl 2.2%

HTML 1.2%

Shell 1%

Makefile 0.6%

Other 0.6%