[Touch-packages] [Bug 2027797] Re: systemd-resolved DNSSEC implementation does not protect against cache poisoning

2023-07-21 Thread Bug Watch Updater
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2027797 Title: systemd-resolved DNSSEC implementation does not protect

[Touch-packages] [Bug 2027797] Re: systemd-resolved DNSSEC implementation does not protect against cache poisoning

2023-07-21 Thread Nick Rosbrook
** Bug watch added: github.com/systemd/systemd/issues #25676 https://github.com/systemd/systemd/issues/25676 ** Also affects: systemd via https://github.com/systemd/systemd/issues/25676 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 2027797] Re: systemd-resolved DNSSEC implementation does not protect against cache poisoning

2023-07-14 Thread Seth Arnold
Thanks for the report; it's my understanding that "real" DNSSEC deployments at sites that care will do all the DNSSEC enforcement with a local recursor because the application APIs are immature / underspecified / etc. Such centralization also makes it far easier for the DNS operations team to

[Touch-packages] [Bug 2027797] Re: systemd-resolved DNSSEC implementation does not protect against cache poisoning

2023-07-14 Thread Petr Menšík
Because systemd-resolved is preinstalled not only on desktop, but also server variant, I expect some people may decide to protect their dns cache. Unfortunately it does not tell them it won't work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,