Security Issues in Matrix’s Olm Library.
(soatok.blog)
from ModerateImprovement@sh.itjust.works to technology@lemmy.world on 14 Aug 2024 19:40
https://sh.itjust.works/post/23697704
from ModerateImprovement@sh.itjust.works to technology@lemmy.world on 14 Aug 2024 19:40
https://sh.itjust.works/post/23697704
I don’t consider myself exceptional in any regard, but I stumbled upon a few cryptography vulnerabilities in Matrix’s Olm library with so little effort that it was nearly accidental.
It should not be this easy to find these kind of issues in any product people purportedly rely on for private messaging, which many people evangelize incorrectly as a Signal alternative.
threaded - newest
FWIW, current versions of the reference client (Element) don’t use the Olm library (libolm), which is now deprecated.
From the README:
Also, from the latest weekly update:
Nevertheless, if you’re using a third-party Matrix client that depends on libolm, you might want to contact its developers, or switch.
How I know if Fractal the gnome app use that library?
I doubt Fractal uses libolm, since it’s a Rust app, but you could ask the developers to be certain.
gitlab.gnome.org/World/fractal
It uses matrix-rust-sdk (written by Element) and that uses the new vodozemac, so you’re safe