https://www.ip-tracker.org/locator/ip-lookup.php?ip=Microsft...
It does seem MS owns that domain, but to be actively using it --- especially for telemetry --- raises red flags for me too. Using misspellings of names is something malware often does.
It does seem MS owns that domain, but to be actively using it --- especially for telemetry --- raises red flags for me too. Using misspellings of names is something malware often does.
It also randomly creates a new service matching the name of an old service + a random changing hexadecimal suffix, and I apparently have Skype running on my gaming rig. As is, I don't consider Windows a defensible platform.
I have the feeling that everyone just keeps slapping features, services and more telemetry onto Win 10 left and right with little coordination. Would be funny if some government agency just told Microsoft "now give us a complete list of all telemetry" - I would be surprised if MS could do it (with any reasonable confidence that the list is actually complete).
[1] https://support.microsoft.com/en-us/help/4023057/update-to-w... [2] https://answers.microsoft.com/en-us/windows/forum/windows_10...
...and they didn't even bother to check that there's an existing project of that name (which will only serve to scare those who come across it by searching --- the description begins "Platform for moderated remote access"...): https://github.com/rempl/rempl
It also randomly creates a new service matching the name of an old service + a random changing hexadecimal suffix
That is extremely disturbing. It's like MS is following in the lead of malware persistence techniques.
There's also this:
https://www.askvg.com/what-are-sedsvc-exe-sedlauncher-exe-fi...
"Hardens the servicing stack against admin tampering." Yes, they're fighting against you, the owner. As the exclamation goes, "fucking bastards!"
All this aggression is going to do is drive even more users who are forced into using Windows 10 to turn off updates completely. They were already wary, now they'll have lost their trust completely.
I did that 6 months ago best thing I ever did to win 10 so far.
I don't understand this type of argument.
your spidey sense is telling you what you need to know, you just won’t say it
Any user-facing names obviously get reviewed by the whole departments that are dedicated to ensuring it fits with the brand, translates well into all languages, not offensive to anyone, etc.
For identifiers that are not expected to be user facing, they're likely to get code review, simple profanity filters, and certificate policy checks, plus whatever bikeshedding those particular dev+ops+networking teams want to have about it. For a service endpoint that's really only resolved in the guts of client code, I could easily imagine an individual dev just using an arbitrary name for the prototype, and then eventually finding that the service became useful and that it's just not worth updating all the existing clients for a cosmetic change mostly no one sees.
Also, you hear conversations like "so-and-so registered that name years ago for idea X, but that didn't really go anywhere, so we can just repurpose that since we know that it's both already working and unused".
So I wouldn't read any particular motivation into 'microsft.com'.