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.09] varnish6: 6.2.0 -> 6.2.1, fixing CVE-2019-15892 #70532

Merged
merged 1 commit into from Oct 6, 2019

Conversation

risicle
Copy link
Contributor

@risicle risicle commented Oct 6, 2019

Motivation for this change

Fixes CVE-2019-15892 https://nvd.nist.gov/vuln/detail/CVE-2019-15892

For master, we should be merging #69973 instead.

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)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @

@ofborg ofborg bot requested a review from fpletz October 6, 2019 15:39
@risicle risicle changed the title varnish6: 6.2.0 -> 6.2.1, fixing CVE-2019-15892 [r19.09] varnish6: 6.2.0 -> 6.2.1, fixing CVE-2019-15892 Oct 6, 2019
@risicle risicle marked this pull request as ready for review October 6, 2019 15:45
Copy link
Member

@fpletz fpletz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@fpletz fpletz merged commit a0b69c1 into NixOS:release-19.09 Oct 6, 2019
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