3 ms·

Signal has security bugs line the best of them. The most famous is probably https://thehackerblog.com/i-too-like-to-live-dangerously-accidentally-finding-rce-in

Signal has security bugs line the best of them. The most famous is probably https://thehackerblog.com/i-too-like-to-live-dangerously-accidentally-finding-rce-in-signal-desktop-via-html-injection-in-quoted-replies/ https://thehackerblog.com/i-too-like-to-live-dangerously-acc... - which gave full RCE, letting the attacker steal all your messages or worse. The two critical bugs in question here were similarly implementation bugs in matrix-js-sdk and its derivatives. Separately, there’s a question over the fact Matrix by design controls group membership on the server… and warns users if malicious devices get added, rather than explicitly forbidding them. We’re fixing that anyway, but it’s questionable if this counts as “issues with e2ee” - it’s similar to deriding Signal for pushing all the users in your addressbook when you join the app(!)

palata 4y ago
> Signal has security bugs line the best of them. I was talking about the Signal protocol. > it’s questionable if this counts as “issues with e2ee” Fair point. It's not a problem in the encryption protocol, but it is a design problem on the group membership control. Now I think it's not completely fair to compare that to the Signal private contact discovery, which relies on SGX enclaves. First, because it's private (if you trust the SGX enclave technology), and second because even if it was not, I believe it is a pretty different level of "design problem": "if the secure enclave does not work, then the server can access a hash of your addressbook" vs "if the whole system works as expected, AND you don't constantly keep an eye on the group members, it could be that a malicious actor reads the content of your messages". Or am I misunderstanding something?