3 ms·
Hopefully matrix packets when encrypted look just like any other encrypted internet traffic. If there are identifying bits there, that's likely a bug in encryp
by necovek 4y ago
Hopefully matrix packets when encrypted look just like any other encrypted internet traffic.
If there are identifying bits there, that's likely a bug in encryption.
- smoldesu 4y agoMatrix packets are encrypted at the application-level of the OSI model. Deep packet inspection relies on inspecting all of the other data about the traffic and using it to block/terminate your connection: https://security.stackexchange.com/questions/20814/does-using-https-tls-s-mime-ssl-e-t-c-protect-you-from-deep-packet-inspectio https://security.stackexchange.com/questions/20814/does-usin... https://en.wikipedia.org/wiki/OSI_model https://en.wikipedia.org/wiki/OSI_model A solid VPN is your best bet at getting around this.
- necovek 4y agoIsn't Matrix protocol basically JSON-over-HTTPS? After TLS connection is negotiated, nodes in the middle have no idea what's going across the wire. E2E encryption simply means that not even Matrix servers can decrypt messages. Sure, you can track connections to existing, well known Matrix servers and act as a HTTPS client to figure out if a server is a Matrix server, but you can make it appear as any web server I guess. You'd probably need to make it not respond to Matrix requests from unknown peers if you want to hide it, so you are right that one could easily block most of publicly accessible Matrix network for sure.