2 ms·
As one of the replies in that thread you linked explains, this is TLS encrypted traffic, so Telia can't really do anything to influence what happens here. They
by tialaramex 6y ago
As one of the replies in that thread you linked explains, this is TLS encrypted traffic, so Telia can't really do anything to influence what happens here. They don't get to see what the traffic means, and if they change any of it then the connection aborts, which doesn't result in a 401 error it just hangs up abruptly - that's how TLS is designed to work.
It is entirely possible that somebody at Signal fat-fingered an IP address block, e.g. some kiddie is spewing 10Gb/s of traffic from 10.2/16 to Signal, but a Signal person blocks 10.20/16 [addresses example only] and only a week later when investigating "Why are we still eating 10Gb/s of spew?" do they realise they typo'd the number.
- upofadown 6y agoI could not find the reference to TLS in the replies. Generally Signal does not use TLS for their messaging system, it is instead something home brewed.
- tialaramex 6y agoSo, what's happening here is that the Signal Desktop app wants a configuration, which it fetches from https://textsecure-service.whispersystems.org/v1/config https://textsecure-service.whispersystems.org/v1/config HTTPS is HTTP protocol spoken over a TLS encrypted channel. When these Telia users weren't able to use the Signal Desktop software, this fetch failed, with a 401 error which is the HTTP error code for Unauthorised.
- INTPenis 6y agoYeah that makes a lot more sense, I was so wrapped up in tinfoil I didn't even think about the TLS. Thanks.