[Touch-packages] [Bug 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf

2023-04-04 Thread Marques Johansson
This is not a matter of CACHE poisoning. This is a 3rd-party owned domain suffix being applied to every name resolution on the system. Users deploying Kubernetes on these nodes will inherit this behavior in kube-dns, for example. Users' applications, package management, pods, and customer

[Touch-packages] [Bug 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf

2023-02-28 Thread Marques Johansson
This is still a problem. Who would set the importance and assign someone to this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1978351 Title: MITM vector: ifupdown

[Touch-packages] [Bug 1978351] Re: MITM vector: ifupdown puts .domains TLD in resolv.conf

2022-06-13 Thread Marques Johansson
Debian 11's ifupdown 0.8.36 does not contain the /etc/network/if- up.d/resolved script that contains the DOMAINS=DOMAINS line. The equivalent functionality in Debian comes from /etc/network/if- up.d/000resolvconf from the resolvconf package. (I don't know if these are standard or if these are