Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[r19.03] powerdns: add patches fixing CVE-2019-10162, CVE-2019-10163 #63969

Closed

Conversation

risicle
Copy link
Contributor

@risicle risicle commented Jul 1, 2019

Motivation for this change

https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2019-04.html
https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2019-05.html

Debian have conveniently fished out the right patches for these.

Note: I have not yet completed a nox-review for this. Ok, there aren't any reverse dependencies.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@risicle
Copy link
Contributor Author

risicle commented Jul 1, 2019

nixos/tests/powerdns.nix is happy for me too (non-nixos linux, x86_64).

@Mic92
Copy link
Member

Mic92 commented Jul 1, 2019

Thanks. I backported the patch release instead since there also seem some interesting bugfixes in it: 85f820d

@Mic92 Mic92 closed this Jul 1, 2019
@risicle
Copy link
Contributor Author

risicle commented Jul 1, 2019

I was kinda trying to avoid that because ... yknow, tiny behaviour changes & all that. Nevermind, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants