Granted, the part
The globally recommended app by privacy and security experts, Signal, is now being downloaded massively and tops the Danish Google Play Store
is a little ironic, but you gotta push this winning tide and then work from that.
Granted, the part
The globally recommended app by privacy and security experts, Signal, is now being downloaded massively and tops the Danish Google Play Store
is a little ironic, but you gotta push this winning tide and then work from that.
An encrypted connection between two endpoints.That’s required for “decentralized open-source messengers”.
Currently it’s impossible to prevent because of all the encrypted video calls of the Meta messengers and similar connections between endpoints.
If those video streams are marked then it is known which endpoints use software that evades surveillance.
I am not sure you understand what you are talking about. There is no easy way to distingish between different connections and pretty much all internet traffic is encrypted these days.
My argument is that a central registry, where all controlled software registers their connections, is all that is needed to identify the connections that are outside the control of the surveillance state.
How would you register all connections of the internet?
Only e2e connections have to be registered.
If every human has 10 e2e connections per hour, that’s 80G connections. If that requires 10k bytes for communication that would be 800T bytes per hour, 250G byte per second. That should be possible.
Use the routers of the exchange points to track the connections. Let them report any connection that hasn’t received a validation from the registry.
Again, what is a “e2e connection”? There is no such thing and it is nearly impossible to distingish a e2e encrypted data stream inside a TLS connection from regular TLS encrypted connection.
It is a connection between network Endpoints. The connection that is e2e Encrypted.
IP ranges show which IP belongs to a server in a data center and which is an endpoint.
Yes, but how do you distinguish between two identical TLS connections? You can’t and hence you can’t figure out if the content inside is additionally e2e encrypted. So what you are suggesting just doesn’t work technically.
The registry tells me if a connection is from an app that uses encryption that I can break. Everything else is suspect, needs investigation and after an introduction time, will be forbidden. Routers can easily discard everything that is not approved by the registry.