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

[20.09] libgcrypt_1_5: mark as insecure #111283

Merged
merged 1 commit into from Jan 30, 2021
Merged

[20.09] libgcrypt_1_5: mark as insecure #111283

merged 1 commit into from Jan 30, 2021

Conversation

dotlambda
Copy link
Member

Motivation for this change

backport of #111215

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.

@dotlambda
libgcrypt_1_5: mark as insecure
bfd1bd8 
(cherry picked from commit 7ca0cef)
@dotlambda dotlambda mentioned this pull request Jan 30, 2021
Merged
10 tasks
@dotlambda dotlambda changed the title libgcrypt_1_5: mark as insecure [20.09] libgcrypt_1_5: mark as insecure Jan 30, 2021
@erictapen erictapen merged commit 638eff2 into NixOS:release-20.09 Jan 30, 2021
@dotlambda dotlambda deleted the libgcrypt_1_5-insecure branch January 30, 2021 09:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
1.severity: security 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
2 participants
@dotlambda @erictapen