it was introduced by commit 08933475abd0580cff747e3d1e0db3865207a200
Signed-off-by: Martin Schiller
---
src/dnsmasq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/dnsmasq.c b/src/dnsmasq.c
index aa29bbf..7fd33af 100644
--- a/src/dnsmasq.c
+++ b/src/dnsmasq.c
@@ -242,7
Hi,
by default in the Debian/Ubuntu package it looks like this:
root@sirius:~# dpkg -l | fgrep dnsmasq
ii dnsmasq 2.79-1all
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.79-1
Hi Simon, I am definitely not a DHCP expert and I don't want either to
become a pain. Yet... I can read that not only the behavior is not inline
with RFC, but it even contradicts the RFC:
"3.2 Client-server interaction - reusing a previously allocated network address
If a client
On Sun, Oct 7, 2018 at 12:05 PM Loganaden Velvindron
wrote:
> On Sun, Oct 7, 2018 at 2:13 PM Rick Thomas wrote:
> >
> > What do I need to do to be ready for the DNSSEC Root KSK (key signing
> key) rollover on October 11, 2018?
> >
>
> Well, dnsmasq already commited a patch for the new trust
> On 8 Oct 2018, at 02:58, Mouath Ibrahim wrote:
>
> Hello,
>
> I ran the PoC supplied by Google research team found here: https://github.com/
> google/security-research-pocs/blob/master/vulnerabilities/dnsmasq/
> CVE-2017-14495.py
>
> and noticed immediately that dnsmasq process uses up
