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

openssl: fix CVE-2016-2177 #17928

Closed
wants to merge 1 commit into from
Closed

Conversation

rasendubi
Copy link
Member

Things done
  • Tested using sandboxing
    (nix.useChroot on NixOS,
    or option build-use-chroot in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • OS X
    • Linux
  • 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/)
  • Fits CONTRIBUTING.md.

Note we can't use fetchpatch because that leads to cyclic dependency.

@mention-bot
Copy link

@rasendubi, thanks for your PR! By analyzing the annotation information on this pull request, we identified @edolstra, @dezgeg and @nathan7 to be potential reviewers

@fpletz
Copy link
Member

fpletz commented Aug 23, 2016

This issue has a very low priority upstream. Even Debian and Red Hat (who don't have the rebuild all dependent packages) didn't update their openssl packages for this issue.

See https://bugzilla.redhat.com/show_bug.cgi?id=1341705 & https://security-tracker.debian.org/tracker/CVE-2016-2177.

So 👎 from me.

@@ -8,7 +8,7 @@ let
opensslCrossSystem = stdenv.cross.openssl.system or
(throw "openssl needs its platform name cross building");

common = { version, sha256 }: stdenv.mkDerivation rec {
common = args@{ version, sha256, patches ? [] }: stdenv.mkDerivation rec {
Copy link
Member

Choose a reason for hiding this comment

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

Why the args@? You can references the patches via patches instead of args.patches.

Copy link
Member Author

Choose a reason for hiding this comment

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

Because it's rec and referencing as patches will produce infinite recursion.

@edolstra
Copy link
Member

We can merge this into staging instead.

@grahamc
Copy link
Member

grahamc commented Aug 25, 2016

Has this been merged in to staging?

@rasendubi
Copy link
Member Author

@grahamc it hasn't

vcunat added a commit that referenced this pull request Aug 25, 2016
vcunat added a commit that referenced this pull request Aug 25, 2016
(cherry picked from commit 801692c)
@vcunat
Copy link
Member

vcunat commented Aug 25, 2016

Now in staging and 16.03.

@edolstra
Copy link
Member

Why was this backported to 16.03 if it's low impact (see #17928 (comment))?

@vcunat
Copy link
Member

vcunat commented Aug 26, 2016

I didn't understand low priority as not worth fixing/cherry-picking.

@grahamc
Copy link
Member

grahamc commented Aug 28, 2016

I think this issue can be closed, since it is good as done?

@fpletz fpletz closed this Aug 28, 2016
adrianpk added a commit to adrianpk/nixpkgs that referenced this pull request May 31, 2024
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.

7 participants