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

fetchmail: 6.3.26 -> 6.4.2 [security] [20.03] #82048

Merged
merged 1 commit into from Mar 9, 2020

Conversation

tokudan
Copy link
Contributor

@tokudan tokudan commented Mar 8, 2020

Motivation for this change

Without this patch fetchmail is practically broken as it still uses an unsupported version of openssl.
This also fixes several security issues that were fixed in fetchmail 6.4.

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.

The new version supports OpenSSL 1.x. Should be back-ported to
release-20.03.

See https://sourceforge.net/projects/fetchmail/files/branch_6.4/
for the changelog.

(cherry picked from commit 85befe9)
@tokudan tokudan changed the title fetchmail: 6.3.26 -> 6.4.2 [security] fetchmail: 6.3.26 -> 6.4.2 [security] [20.03] Mar 8, 2020
@tokudan
Copy link
Contributor Author

tokudan commented Mar 8, 2020

@GrahamcOfBorg build fetchmail

@lsix lsix merged commit 7010635 into NixOS:release-20.03 Mar 9, 2020
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.

None yet

4 participants