Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Matrix is 100% open-source.

It's still astonishing to me that people think that open source somehow has any bearing on the issue of:

> Nobody can say what the server is doing nor what it is harvesting which could be very dangerous.

Thats still true, whether its running open source software or not. You cannot inspect the running code on a server, except, now you have to trust a whole federated mob of servers.



As someone who doesn't know much about it, would a malicious homeserver have any way to break the end to end encryption, save for putting massive amounts of men in the middle between each conversation which would be busted the second anyone decides to compare public keys?


Clients always need a way to re-negotiate keys in case one user decides to switch to new device and not import keys.

The problem is, say a MITM attack really happens. What is the user going to do? Will they assume it's a bug, will they press "accept" blindly without checking the fingerprints? Will they contact The Intercept to reveal MITM attacks are taking place? Will the press take their claims seriously? Will anyone on the internet drowning in misinformation, disinformation really care?

Then there's the key exfiltration problem. Snowden was very vocal about it at the beginning of the leaks. The NSA goes around E2EE by hacking endpoints and stealing keys. That's not a reason not to use E2EE of course, there are simply more threats with less capabilities but still, threats that are insane amounts of less risk-averse, who won't give two shits about e.g. abusing plaintext data exfiltrated from the server. My point is if you have to deal with risks such as MITM you're probably dealing with adversaries willing to infect your endpoint as well, so you might not detect MITM attacks. For that you need better endpoint security architecture with some guarantees against key/pt exfiltration.


With some important caveats, this situation is what remote attestation / SGX secure enclaves are hoping to improve.

https://signal.org/blog/private-contact-discovery/


The solution is to get rid of the servers, as per https://matrix.org/blog/2020/06/02/introducing-p-2-p-matrix.


Serverless architecture in many cases leaks the IP-address to the opposing party (without by-default anonymization via Tor). Cryptography is just math, nothing magical happens when p2p is applied, there's still a MITM risk, but there's no scalability issue in compromised IX-routers doing MITM against p2p system users, when compared to compromised Matrix servers doing MITM on mass scale. Less packet filtering but nation state adversaries don't exactly throw in the towel when they need to filter packets by protocol.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: