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

spotify: use default libgcrypt / libpng #111227

Merged
merged 1 commit into from Jan 30, 2021

Conversation

9999years
Copy link
Contributor

Instead of overriding libgcrypt with the (insecure) libgcrypt_1_5 and libpng with libpng12, use the defaults for those two packages.

spotify was changed to use libgcrypt_1_5 instead of libgcrypt in commit 165cb05 by @monocell in PR #8157 to address #8156, which found that:

the current spotify client seems to depend on libgcrypt.so.11. Pretending with libgcrypt.so.20 produces an error like:

... libgcrypt.so.11: version `GCRYPT_1.2' not found ...

Given that the relevant Spotify client is more than 5 years old, I don't think we have to worry about this any more. :)

Built and checked on my NixOS desktop machine because @dotlambda said he wouldn't check proprietary software in #111215.

This commit helps #106203, but doesn't close it because libgcrypt_1_5 is still used in staruml.

Motivation for this change

libgcrypt_1_5 has a heap overflow vulnerability; removing it is blocked on removing it from spotify and staruml.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • 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 nixpkgs-review --run "nixpkgs-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.

Instead of overriding `libgcrypt` with the (insecure) `libgcrypt_1_5`
and `libpng` with `libpng12`, use the defaults for those two packages.

Built and checked on my NixOS desktop machine because @dotlambda said he
wouldn't check proprietary software in NixOS#111215.

`spotify` was changed to use `libgcrypt_1_5` instead of `libgcrypt` in
commit 165cb05 by @monocell in PR NixOS#8157
to address NixOS#8156, which found that:

> the current spotify client seems to depend on `libgcrypt.so.11`.
> Pretending with libgcrypt.so.20 produces an error like:
>     ... libgcrypt.so.11: version `GCRYPT_1.2' not found ...

Given that the relevant Spotify client is more than 5 years old, I don't
think we have to worry about this any more. :)

This commit helps NixOS#106203, but doesn't close it because `libgcrypt_1_5`
is still used in `staruml`.
@9999years 9999years mentioned this pull request Jan 29, 2021
10 tasks
@dotlambda dotlambda added the 9.needs: port to stable A PR needs a backport to the stable release. label Jan 30, 2021
Copy link
Member

@erictapen erictapen left a comment

Choose a reason for hiding this comment

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

Builds for me on x86_64-linux.

@erictapen erictapen merged commit a61c57a into NixOS:master Jan 30, 2021
@erictapen
Copy link
Member

Backport in 3c0ade1. I also only built it on the release branch.

@erictapen erictapen added 8.has: port to stable A PR already has a backport to the stable release. and removed 9.needs: port to stable A PR needs a backport to the stable release. labels Jan 30, 2021
@9999years 9999years deleted the spotify-update-libgcrypt branch January 30, 2021 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.has: port to stable A PR already has a backport to the stable release. 10.rebuild-darwin: 0 10.rebuild-linux: 1-10
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants