On Sat, Nov 26, 2022 at 10:34:28AM -0800, Sam Trenholme wrote:
>...
> If someone can not step up to plate to maintain MaraDNS for Debian, we
> should deprecate and eventually remove the package.
>
> I may end up making my own .deb files for MaraDNS.
It would also be an option for you to become th
[1] RFC8482 responds to ANY in such as way as to not break Qmail
On Sat, Nov 26, 2022 at 10:34 AM Sam Trenholme wrote:
>
> Upstream here again. I have released MaraDNS 3.5.0030 and 3.4.09 with
> a security update: MaraDNS now fully supports RFC8482, which means
> MaraDNS no longer supports ANY r
Upstream here again. I have released MaraDNS 3.5.0030 and 3.4.09 with
a security update: MaraDNS now fully supports RFC8482, which means
MaraDNS no longer supports ANY records. [1] While MaraDNS does not
have long packet support, this removes one possible denial of service
amplification path.
If
Upstream here. I should probably summarize the security issues post
2.0.13; MaraDNS is the authoritative server and Deadwood is the
recursive server:
- A theoretical issue with the cryptographic code which doesn’t affect
gcc and clang compiles of Deadwood.
- An issue where a clever attacker could
Source: maradns
Version: 2.0.13-1.4
Severity: serious
The last maintainer upload was in 2015 and the version currently in the
archive is way behind current upstream releases (which is at 3.4.07),
we have plenty of maintained DNS servers, keep it out of testing (
and if noone picks it up, remove it
5 matches
Mail list logo
