3 ms·
> Because it's open-source, has been reviewed extensively, and people (with various degrees of expertise) keep looking at it. Sooo your security is based on bl
by Andrew_nenakhov 5y ago
> Because it's open-source, has been reviewed extensively, and people (with various degrees of expertise) keep looking at it.
Sooo your security is based on blind trust in some people out there who definitely do keep looking at Signal's apps, somehow verify that every shipped version of their app contain the same code as their open source repository? That's a lot of trusting.
(Wouldn't it be simpler to just trust Signal not to watch what you are texting to your significant other, and keep everything without encryption, saving yourself a lot of trouble?)
> E2EE on Signal means I don't have to trust that some employees won't abuse their rights to access my data.
So your threat model are Signal's employees who might be stalking you? You know, you could run a $2/month xmpp server that would serve you just fine, and you wouldn't have to worry about any threat of this kind. This not-working-federated-protocol is surprisingly effective in sending and receiving messages.
- hiq 5y ago> Wouldn't it be simpler to just trust Signal not to watch what you are texting to your significant other This doesn't hold in practice, you simply cannot trust any single entity about this, since it's bound to be abused eventually. > You know, you could run a $2/month xmpp server that would serve you just fine, and you wouldn't have to worry about any threat of this kind. So instead of managing my client, I need to manage both my client and a server, and trust this server on top of the client? That's obviously worse, I'm starting to think you're trolling.