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.

Sign up for GitHub

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

Jump to bottom

mono44: remove insecure version #49368

Merged
merged 1 commit into from Oct 28, 2018
Merged

mono44: remove insecure version #49368

merged 1 commit into from Oct 28, 2018

Conversation

Mic92
Copy link
Member

@Mic92 Mic92 commented Oct 28, 2018 •
edited

This version is also affected by CVE-2018-1002208.
It has no users in nixpkgs.

Motivation for this change
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 nox --run "nox-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)
  • Fits CONTRIBUTING.md.

@Mic92
mono44: remove insecure version
80d4263 
This version is also affected by CVE-2018-1002208.
It has no user in nixpkgs.
@Mic92 Mic92 merged commit ea30c71 into NixOS:master Oct 28, 2018
@Mic92 Mic92 deleted the mono-cleanup2 branch October 28, 2018 23:11
@Mic92
Copy link
Member Author

Mic92 commented Oct 28, 2018

Marked as insecure in stable: c05b365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@c0bw3b c0bw3b c0bw3b approved these changes

Assignees
No one assigned
Labels
1.severity: security 8.has: clean-up 10.rebuild-darwin: 0 10.rebuild-linux: 0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@Mic92 @c0bw3b @GrahamcOfBorg