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
munin: 2.0.30 -> 2.0.33; for CVE-2017-6188 #24182
Conversation
@domenkozar I think |
I tested the service manually on unstable, somebody who can test it in 16.09? |
ping maintainers: @domenkozar or @bjornfor do you have a chance to tests this on 16.09? |
@Mic92: This doesn't apply cleanly on release-16.09: we need to cherry-pick a couple of other munin commits before this one. I can test / backport to release-16.09 after this gets merged to master. |
@bjornfor here we go. |
@Mic92: Building my system on release-17.03 now. (First backporting to release-17.03, then 16.09) |
Applied to release-17.03 and release-16.09. I ran the NixOS test for munin (nixos/tests/munin.nix) and also tested both branches manually by looking at the log (nothing suspicious) and that it produces graphs (in my browser). |
@bjornfor thanks |
Motivation for this change
Update;
Also to fix CVE: NixOS/security#36
Upstream Bug:
munin-monitoring/munin#721
Please test, as I am unsure how this app/program works
Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)