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

[24.05] olm: mark as vulnerable #335189

Merged
merged 4 commits into from
Sep 2, 2024
Merged

Conversation

emilazy
Copy link
Member

@emilazy emilazy commented Aug 16, 2024

Description of changes

Manual backport of #334638.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

CVE numbers were assigned, and This Week in Matrix included an
announcement from the Matrix.org project lead. An official post from
the Matrix.org Foundation is apparently still pending.

(cherry picked from commit 069f7de)
@emilazy
Copy link
Member Author

emilazy commented Aug 25, 2024

Now also backports #336828. I will merge this once #336901 hits 24.05.

Additional information has been published by upstream about why they
believe the vulnerability to not be exploitable over the network:
https://matrix.org/blog/2024/08/libolm-deprecation/

This commit

* updates the text of the vulnerability warning to indicate that
  upstream does not believe the issues to be exploitable over the
  network, and
* adds a link to the blog post.

Co-authored-by: Emily <hello@emily.moe>
Signed-off-by: Sumner Evans <sumner.evans@automattic.com>
(cherry picked from commit 537d3c4)
@emilazy emilazy merged commit cbff61b into NixOS:release-24.05 Sep 2, 2024
22 of 24 checks passed
@emilazy emilazy deleted the push-zrsuyznoqtmp branch September 2, 2024 02:41
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.

2 participants