this post was submitted on 31 Dec 2021
40 points (90.0% liked)

Open Source

31118 readers
961 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

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

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!

you are viewing a single comment's thread
view the rest of the comments
[–] dessalines@lemmy.ml 9 points 2 years ago (1 children)

How does xmpp not store information about federated users joining a room?

[–] poVoq@lemmy.ml 8 points 2 years ago* (last edited 2 years ago) (1 children)

XMPP only does this on the single server the room resides on and does not share this info with other participating servers except for the bare minimum needed to show the users nick names.

I recommend you hosting your own Matrix home server and after joining a few federated rooms look at your database what kind of historical metadata ends up on your new server. It's honestly appalling from a privacy point of view.

Yes this is needed for room persistence across multiple servers, but IMHO that is a solution looking for a problem and also a highly over-engineered one.

[–] Ferk@lemmy.ml 7 points 2 years ago* (last edited 2 years ago)

There's ongoing work to encrypt much of the metadata. https://github.com/matrix-org/matrix-doc/pull/3414

Yes this is needed for room persistence across multiple servers, but IMHO that is a solution looking for a problem and also a highly over-engineered one.

Without this solution the transition to p2p would be much more complicated, would it not?