4 ms·
Telemetry related of course. Shame it is not properly documented. As with all things closed source we have no idea how this works, when it is updated or if it i
by satysin 10y ago
Telemetry related of course. Shame it is not properly documented. As with all things closed source we have no idea how this works, when it is updated or if it is possible to ignore it totally.
- besselheim 10y agoLooking at the list of domains, they appear to be almost entirely unrelated to telemetry. Most likely this feature is a response to incidents such as this: https://www.wired.com/2011/03/comodo-compromise/ https://www.wired.com/2011/03/comodo-compromise/ (in which certs for login.skype.com and login.live.com were misissued by Comodo). Blocking the domains in this list to prevent telemetry, as suggested in other comments, would prevent access to most of Microsoft's online services. This includes third-party websites hosted on Azure that aren't using their own custom domain (.azurewebsites.net), and all software updates, including critical security patches.
- TazeTSchnitzel 10y agoI recall seeing a list of telemetry domains, and it's quite different. This is a list of user-facing sites.
- dirtbox 10y agoCorrect. I made a quick dump of the telemetry hosts here: https://cl.ly/hZ3q https://cl.ly/hZ3q If you have win10, you can add this to your hosts file. The optional portion of the list will block store items, the email client and even things like the Groove media player, so use it as you will.
- lightedman 10y agoGiven the OS is known to be able to ignore its own HOSTs file, you're better off doing this directly in your router, if that is a possible option.
- dirtbox 10y agoUnless you have a source that shows otherwise, I only know if it doing that if it's formatted wrongly, which is going to be a problem with most things.
- deleted 10y ago[deleted]
- Maarten88 10y agoMaybe Microsoft are trying to foil m.i.t.m. attacks against their infrastructure, by reporting back certificate errors for those domains. A hacker who is developing an attack against Windows Update will need to implement a mock version of the service, redirect dns, and create self-signed certs for those domains. I think Microsoft are interested in people/organizations doing that. Of course, this is not foolproof, and documenting the feature will just alert people they need to mock telemetry and this pinning feature first.
- akerro 10y agoDidn't Stallman warn us about it?