4 ms·
You and a large number of others would like to know what is in the telemetry. If I recall correctly, the problem is that it's all TLS wrapped with pinned certs
by kardos 10y ago
You and a large number of others would like to know what is in the telemetry. If I recall correctly, the problem is that it's all TLS wrapped with pinned certs (no source on that at the moment). You'd be doing the internet community a favour if you figured out a way to decode the "telemetry" packets to see what's actually in there.
- satysin 10y agoYeah network capture isn't going to be any use as it is all encrypted. I was wondering if anyone had registry and file system captures on what was being collected, if that is even possible. It wouldn't surprise me to see Microsoft using private APIs to collect data and bypass monitoring tools. If they are it would look even worse though. All of the FUD and other misinformation from random people on YouTube is annoying. I just want a straight answer.
- chli 10y agoThe "private API, telemetry data doesn't go the normal route through the stack" is claimed in the most recent release of "Canard PC Hardware" (n°29) which is a half decent french computer magazine.
- pjc50 10y agoI'm still kind of surprised this hasn't been reverse-engineered. It ought to be possible to find the process that's doing it and hijack its use of the crypto DLLs to record what data is passed in. Do you still get telemetry data when it's run in a VM?
- nikbackm 10y ago> I'm still kind of surprised this hasn't been reverse-engineered. Yeah. Maybe another sign of Microsoft's increasing lack of relevance if no enterprising hacker cares to investigate it.