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

libgcrypt_1_5: mark as insecure #111215

Merged
merged 1 commit into from Jan 30, 2021

Conversation

dotlambda
Copy link
Member

Motivation for this change

closes #90845 and closes #106203

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.

affects spotify (cc @9999years @samuela @timokau) and staruml (cc @flokli @oxalica)

@dotlambda dotlambda added 1.severity: security 9.needs: port to stable A PR needs a backport to the stable release. labels Jan 29, 2021
@SuperSandro2000
Copy link
Member

staruml is the only user of this package. Maybe it can be upgraded than we could drop the version entirely.

@dotlambda
Copy link
Member Author

staruml is the only user of this package.

No, spotify is using it too.

@samuela
Copy link
Member

samuela commented Jan 29, 2021

I don't have a desktop nixos machine to test this on at the moment but the spotify fix should be very straightforward.

@dotlambda
Copy link
Member Author

I don't have a desktop nixos machine to test this on at the moment but the spotify fix should be very straightforward.

Of course it's straightforward, but I won't be testing proprietary spotify either.

9999years added a commit to 9999years/nixpkgs that referenced this pull request Jan 29, 2021
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
Copy link
Contributor

Removed libgcrypt_1_5 from Spotify and opened #111227. Hoping we can get this taken care of quickly, thanks everyone for your work on it!

erictapen pushed a commit that referenced this pull request Jan 30, 2021
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 #111215.

`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. :)

This commit helps #106203, but doesn't close it because `libgcrypt_1_5`
is still used in `staruml`.
erictapen pushed a commit that referenced this pull request Jan 30, 2021
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 #111215.

`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. :)

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

(cherry picked from commit a61c57a)
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.

On 20.09 bracket also uses libgcrypt_1_5, as 89cb93a wasn't backported.

As I currently don't see an effort to upgrade staruml and I'm not very motivated to do it myself I think we should just merge (and backport) this.

@SuperSandro2000 SuperSandro2000 merged commit ffc9c03 into NixOS:master Jan 30, 2021
@dotlambda dotlambda deleted the libgcrypt_1_5-insecure branch January 30, 2021 09:14
@dotlambda
Copy link
Member Author

backport: #111283

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants