4 ms·
Just be aware that Nheko has still uses the deprecated libolm (which has known security issues and is unmaintained) and the maintainers have said they are not i
by cyphar 1y ago
Just be aware that Nheko has still uses the deprecated libolm (which has known security issues and is unmaintained) and the maintainers have said they are not interested in moving to the supported replacement library[1] for the past year. As a fellow Matrix user, I would be cautious about using E2EE with any third-party clients -- the history of issues for the past decade speaks for itself.
[1]: https://github.com/Nheko-Reborn/nheko/issues/1786 https://github.com/Nheko-Reborn/nheko/issues/1786
- bigstrat2003 1y agoThanks for the heads up. I'm not so much interested in E2EE, but I'll have to look into the security issues. I use Nheko because I can't stand how bloated Element is (thanks, Electron), and appreciate the lightweight client. But I do want to not open security holes in the process, of course.
- mananaysiempre 1y agoThe replacement library looks to be effectively Rust-only for now, so while I’m not thrilled with the E2EE situation there I can’t blame the maintainers for not wanting to complicate their build.
- Klonoar 1y agoRight, they shouldn’t have to deal with complications just to ship a correct product. (Massive /s in case it’s not obvious - they should suck it up and migrate)