Re:Amazon threatens to suspend Signal's AWS account over cen...
by seba_dos1 on Tuesday May 01, 2018 @04:23PM
(#16971147)
At least in case of XMPP, the client doesn't need to be able to connect to other domains, so as long as you can connect to your own server outside of the censorship's reach (which could be accessible for c2s connections in a completely different way than for s2s), you should be fine.
[ Parent
| on HN ]
Re:Amazon threatens to suspend Signal's AWS account over cen...
by Paul-ish on Tuesday May 01, 2018 @04:41PM
(#16971350)
How do you ensure the censor doesn't block the major c2s connections? I suspect most techniques are too technical for your average user.
Re:Amazon threatens to suspend Signal's AWS account over cen...
by Boulth on Tuesday May 01, 2018 @04:53PM
(#16971490)
Modern clients can connect via port 443. There is also support for XMPP via WebSockets, that looks like regular HTTPS traffic.
Re:Amazon threatens to suspend Signal's AWS account over cen...
by majewsky on Tuesday May 01, 2018 @05:24PM
(#16971817)
Sure, but they can just block the IP.
Re:Amazon threatens to suspend Signal's AWS account over cen...
by Boulth on Wednesday May 02, 2018 @01:59AM
(#16974451)
Yes, but it's always possible to block IP (targeted attack). Federated with a big amount of small servers make it hard to automate. You can block several hosts but the rest of the network would work fine. And because of how federation in XMPP works you just need a one client to server connection to reach the entire network.