This posts is a list of all the suspicious things Matrix/New Vector and Element (which is run by Matrix employees) have done.
Crossposted to c/opensource from c/privacy.
I want to start a civil discussion on this topic, if anyone has improvement ideas for the list or wants to debate one of the bullet points for removal, I’m all ears.
Matrix
- Matrix was created inside of an Israeli Intelligence Corporation called Amdocs.
- Matrix leaks lots of metadata, in many cases not fixed to date. The homeserver can and does store lots of metadata.
- Even if you run your own instance, it still sends data to the main homeserver.
The Cloudflare Situation
All research on the Cloudflare situation is done by me.
If you check the SSL Certificate for https://element.io you’ll see it’s by Cloudflare.
Cloudflare has MANY privacy issues, and just wanting to centralize the web.
The Element client is the most used client, with many users using the default instance, because it’s easy or they want to simply join their friends or a community on Matrix easily. This comes as worrying because Cloudflare decrypts TLS traffic and this is even more worrying because Cloudflare is a honeypot.
Even if Cloudflare cannot decrypt anything because of the Matrix protocol encrypting them beforehand, lots of metadata in the message itself is send over plaintext like who you’re talking with, channel name etc. (and this is excluding the metadata leaks that Matrix has to the main homeserver and in general). Of course, this could be mitigated by using Element on another instance that isn’t behind Cloudflare, but the average user will not know to do that or even understand the concept of federation and decentralization.
Cloudflare’s CDN can be used without using their SSL certificate which just backdoors your site, so why is Element using it? Element is run by the same people that are behind matrix.org (mostly), so they know how to do basic privacy features.
Even if we assume there’s no ill intent here, Cloudflare just wants to centralize the web (~30% of SSL traffic goes through Cloudflare, ~80% of CDN traffic goes through Cloudflare), which is obviously against Matrix’s mission of decentralized communication.
Through Cloudflare, an adversary with ill intention could target a Matrix user and be susceptible to metadata collection.
The CIA & NSA admitted that they kill people by gathering and using metadata.
I’ve took this argument in the official Matrix channels, and no one has been able to properly respond to the arguments presented. Though, they were only members, no admins were involved.
If anyone wants to bring these issues forth to the official Matrix admins, I’d be more than glad to help. Thanks for reading!
I feel the same, Telegram and Matrix got hyped and whatnot but same like Signal they got millions of dollars and are light years behind the competition. Which makes me wonder what they do with the money and why they do not hire competent people, which I would do in such case to address all concerns and design flaws.
Matrix encryption is flawed too, avatars, reactions etc. are NOT encrypted. Matrix might be an alternative until all flaws are fixed, but that might take years from now.
Most messengers only encrypt the text body. There is some work underway to improve this in XMPP with a new version of the OMEMO standard, but this is not yet implemented in most clients.
IMHO the bigger problem with Matrix’s OLM e2ee is that they weakened key exchange to be per account and not per device (mainly to make it more scalable in group-chats) and this requires devices to exchange the shared private key which is inherently risky.
There is some risk, sure. I don’t see how this would be any more risky than a TLS exchange. Obviously the exchange can be implemented badly, but if done correctly it seems like it would work with certs and send the key encrypted.
I think the bigger risk is the key sitting at rest on multiple devices, some of which are easily lost (cell phones) and could then compromise an account.
You seem to have a misunderstanding of what public and private keys are. Private keys should never leave the device they were created on, and yes of course having the same key on multiple devices is also a problem.
Agreed, many people would like to use what they call “integrations” aka “bots” for those coming from Discord, which wouldn’t be unencrypted, and as you mentioned stickers. Signal/XMPP is my messenger of choice at the moment.