Before everybody goes jumping ship to @TutaPrivacy because of the Proton situation, it's worth knowing they will straight up turn off encryption given a valid court order https://t.co/ElyJ13eX9K
@coah80 i should clarify this is an undocumented endpoint and i have no clue if it's actually based on lavarand (or if it's sufficiently random at all). nonetheless it's a cool party trick that works on any cloudflare site
You can get an approximate edge-to-origin timing on most Cloudflare sites by subtracting the latency of /cdn-cgi/trace (hits edge only) from your normal requests' latency.
If you have a bunch of proxies you can cycle between edges and get a good idea of the origin's geoloc
@MinoaCat my idea here is that you can reduce noise by measuring only the edge's latency to the origin, *excluding* the client-to-edge trip, which tends to be less predictable.
sites like this are fine but they measure the whole client-to-edge-to-origin trip
@Pirat_Nation The GDID was only found *after* they discovered his Microsoft account, which was tied to an email address he used on a cybercriminal forum.
I don't think there's any secret telemetry going on here, his browsing history was likely obtained because he had cloud-sync turned on.
@GooningOnTumblr @vxunderground this is plausible, they had known his identity and the fact that he had a Microsoft account for years before the ngrok even came into the picture.