ZDNet Writer Downplays Windows 10's Phoning-Home Habits
jones_supa writes: Gordon F. Kelly of Forbes whipped up a frenzy over Windows 10 when a Voat user found out in a little experiment that the operating system phones home thousands of times a day. ZDNet's Ed Bott has written a follow-up where he points out how the experiment should not be taken too dramatically. 602 connection attempts were to 192.168.1.255 using UDP port 137, which means local NetBIOS broadcasts. Another 630 were DNS requests. Next up was 1,619 dropped connection attempts to address 94.245.121.253, which is a Microsoft Teredo server. The list goes on with NTP, random HTTP requests, and various cloud hosts which probably are reached by UWP apps. He summarizes by saying that a lot of connections are not at all about telemetry. However, what kind of telemetry and data-mined information Windows specifically sends still remains largely a mystery; hopefully curious people will do analysis on the operating system and network traffic sent by it.
See? Microsoft knows that ONLY apps can app apps, which is why these apps are apping other apps while apping apps!
Apps!
Adding [forbes.com] to forbes links on the front page?
I am bothered by the explicit policy of tracking everything I do within my OS. That is the real issue. That is why I am leaving Windows forever.
Sure, traffic is probably encrypted, but since your system is encrypting it, surely there's a way to discover the keys and find out exactly what data is being sent.
I personally don't have either the time nor the kernel hacking skills to pull it off, but I'm sure somebody could.
Apparently it's some apologism for Windows 10, but an unbelievably poor one. "Oh no, no no! Please don't panic because Windows phones home to over 100 different servers even when you turn the telemetry off. It's probably, eh... nobody's quite sure, but I'm sure everything will be okay!"
This is supposed to be comforting?
They gave away at least a few billion dollars' worth of revenue when they gave away Windows 10 for free. So the kind of telemetry they are collecting is at least worth a few billion dollars. Anyone who says different is lying. There is no free lunch.
Seven puppies were harmed during the making of this post.
"These aren't the droids you're looking for"
Yes, they probably are
The only thing necessary for evil to triumph is for it to be pitted against a slightly greater evil
You can't even listen to music on OS X or iPhone without the software contacting Apple.
Actually, yes I can.
Quo usque tandem abutere, Nimbus, patientia nostra?
You can't even listen to music on OS X or iPhone without the software contacting Apple.
I'm quite tired of this nonsense rebuttal. When you use an Apple application, it contacts Apple's servers to see if there are updates available--you can turn that off as well. In contrast, when do you even the most mundane things in Win10 (with the telemetry turned off, mind you), the OS contacts over 100 different domains: https://github.com/WindowsLies...
Why the fuck does Win10 contact telemetry.appex.bing.net, ad.doubleclick.net, and watson.live.com whenever you open the fucking Notepad?
Even if this is true, so what? It doesn't excuse it in the slightest. Go make an article about OSX or iOS.
The bottom line is that Windows 10 is significantly worse than Windows 7 and 8 in the privacy department. And this has to be pointed out.
Well, since the article is a reaction to "Windows is sending your more personal information back to MS *thousands* of times per day," I'd say yes. It's not so much about comfort as a realistic approach to evaluating what is sent.
My computer phones home to Google thousands of times a day, too. Of course, it's getting my mail, my calendar, and other data, along with the telemetry it's collecting. But, you know, I should be absolutely petrified that Google is spying on me with all that data going back and forth. I suppose.
Is it just my observation, or are there way too many stupid people in the world?
Some of use don't have the luxury of not using Windows, either because we need to run applications that are only on Windows or we work with or support others who cannot be forced off Windows. What we really need is a hardware firewall that blocks all access to Microsoft domain names and IP addresses. Or even better one that sends bad data to Microsoft. Maybe a nice little distributed computing project would be to know what data Microsoft is collecting and the write and distribute software that keeps feeding Microsoft bogus data to make their data collection less useful. If enough people ran such software, and I believe a lot of people would gladly do it no matter if the were Windows or Linux users, Microsoft might get the message and cut this out.
I'm an American. I love this country and the freedoms that we used to have.
with the telemetry turned off
How? Last time I checked telemetry couldn't be disabled on 10, not even on the Enterprise version (go read the "fine print" on Microsoft's website, it's quite sneaky).
https://technet.microsoft.com/library/mt577208%28v=vs.85%29.aspx
Once every day or so: "here are the Microsoft packages installed, are there any updates ?" That does not include: non Microsoft packages, hardware info (other than needed to choose packages), disk/net/cpu/... usage, local account/user info, package usage/popularity, lists of: file names, web sites visited, ...
It looks more like thousands of examples of DNS, NTP, NetBIOS and other perfectly normal and required traffic for any system that is connected to a network or the internet. I mean nearly all of these examples are basic network functionality. Most of the rest are things like OS updates, application updates, applications downloading scheduled data (weather, news, etc.). I know this is /. and we are all supposed to hate MS and Winblow$ like it's still 1999, but can we at least TRY to apply some logic and reasoning to our hating?
The article claiming Windows 10 telemetry phoned home a ridiculous amount of times even when disabled was false. The user who conducted the experiment set telemetry to basic rather than turning it off. Furthermore, some of the apps that might make connections, what's known as the Windows out of the box experience, were not disabled. Furthermore, the router was configured to drop all outbound connections. As a result, the failed attempts to connect resulted in retrying or connecting to different mirrors over and over again. For some services like Windows Update this is completely reasonable behavior, otherwise they'd be vulnerable to a denial of service attack against the update server. The methodology exaggerated the amount of connections made by Windows while not even properly disabling telemetry. These are the facts. One reputable Slashdot user noted that when telemetry was disabled fully in the Enterprise version of Windows and all of the other apps were disabled, the only outbound connections were, in fact, Windows Update.
Despite the facts, Slashdot users complain about any story that suggests that Windows 10 telemetry isn't as severe as it's made out to be and accuse the authors of being Microsoft shills. Furthermore, these Slashdot users get modded up, and the parent is at +4 insightful. It seems that facts are optional in these discussions, and that's a shame. Those who make such false claims about Linux distros such as Ubuntu are rightly accused of being trolls and modded accordingly. But doing that to Microsoft is insightful.
Those of you who post such things and mod up such posts should be ashamed of yourselves. If privacy advocates want to be taken seriously, the discussions need to be based on facts instead of FUD. There are real issues with Windows telemetry namely that users are automatically opted in without being prompted, that Microsoft hasn't disclosed what data are sent to them, and that only the Enterprise versions of Windows 10 can fully disable the telemetry. These are real issues. But when there's so much FUD and misinformation, it damages the credibility of those who raise very legitimate objections. You should be ashamed of yourself for posting false information because it does a disservice to those with very real concerns about privacy.
Just the fact that it it phoning home is enough to reveal some information, such as that the device on the other end is running Windows 10. Looks like it's also trying to discover any other machines on the local network.
Oh, the humanity!
If it's suspicious activity that wasn't disclosed ahead of time, it should be considered nefarious until proven otherwise. Your machine is not under your control ... that's a serious problem.
I'll assume you never use a smartphone, a user friendly Linux distribution (or *BSD ditto) etc.? Even browsing the web would make the machine "not under your control" so I guess you use telnet to communicate with /. servers.
Either that or your post is essentially useless.
They're one of the harder corporate shills. Microsoft or Apple, they know no bounds in selling out.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
But his point about "if the guy had let the connections go out - especially HTTP which you can just sniff - we might know for certain what it was actually trying to send out" is more than spot-on enough to compensate.
And if you're worried, block port 80 to those ranges of IPs.
Why the fuck does Win10 contact telemetry.appex.bing.net, ad.doubleclick.net, and watson.live.com whenever you open the fucking Notepad?
Because Cortana?
Cortana: It looks like you are trying to type some letters. Would you like help?
Why are a Windows 10 box in 2016 actually sending out freaking NetBIOS broadcasts for? That shit should be dead and buried decades ago.
Where I work, and at most of the companies I have worked for, the vast majority of the software used, ran on Windows.
Whether it was servers or workstations, Windows was the choice. This was because the software used could only be ran on Windows. I suspect there are many companies/government agencies/schools, etc that are in that same situation. Sure, there may be a *nix server here, an Apple product there, etc, but Microsoft definitely has the stranglehold.
Since Microsoft is in this position, and the software used by my workplace runs only on Windows, there will eventually come a time, when vendors have put out versions of their software that will run on WX, that all workstations in our workplace will be WX. I don't see this NOT happening.
This means, that unless someone took the time to configure a firewall to block all of the telemetry, etc, connections going out to Microsoft's "user data and profiling aggregation infrastructure", anything someone did on one of those WX machines, while at work, would essentially be tracked and logged by Microsoft and whoever they were sharing that data with.
I don't think people really understand what this means.
Oh, and do me a favor. Please don't suggest I use Linux. If a workplace like mine, or the others I've been at, could have used Linux instead of Windows, that transition would have happened years ago.
And another thing, there is a false sense of privacy among many about BYOD. As if using your iPhone or Samsung is going to leave you a trail free of crumbs. Free from every comment you make online, free of every post or update.
We play the game with the bravery of being out of range
Even after the moronic voat user was shown to have completely screwed up the entire test slashdot is here referencing it yet again as fact? The new editors - just as shitty as the old ones.
BeauHD. Worst editor since kdawson.
With the exception that if you disable it, it actually IS disabled. If you don't use features that specifically require online contact (eg: Siri, Genius, Apple Music, etc) then it doesn't. (AFAIK)
NetBIOS over TCP is still a core part of Microsoft networking and the broadcasts allow the various machines running Windows or SAMBA to discover each other without needing a central directory server. It is still implemented because it is a useful API with decent backward compatibility with everything back to 95/98.
This isn't the old NetBIOS Frames line protocol from the extremely old days, rather the service layer protocol that handles the discovery, negotiation and authentication parts of peer-to-peer file and printer sharing in Windows.
Trying to become famous by taking photos. Visit my homepage please.
DNS queries aren't "spying."
Yes, actually they can be. I don't want Microsoft to know that I read deepdotweb anymore than I want the government to know that. Why is microsoft resolving names for Windows 10 users? And who are they sharing the logs with?
This Windows 10 apologist has nothing to offer as an acceptable excuse for this behavior.
I have DNS servers already, how is sending dns queries to microsoft not spying?
Sorry, teleporters just kill you and then make a copy. A perfect, soul-less copy.
I don't use Windows on my computers (I do have a Windows phone) so I don't have a dog in this fight but... Err... You know what telemetry is, right? I mean, you can (and should) be able to turn it off if you want and off should mean off - no questions asked. But, umm... If they don't know how you use the OS then they won't be *likely* to consider your use-case when they make changes. They won't know that you're one of the people with that video card and having that problem so they won't fix it if you don't send crash reports. They won't be able to optimize their personal assistant thing if you don't let them have that personal data.
Now, to be clear, I'm a firm believer in off means off. But, it's incumbent on you to know what the outcome of your choices may be. Oh, they might get enough reports about that driver and video problem but what if your peers also shut it off? This goes in both directions, actions have consequences. I don't know what the outcome will be but I'm pretty sure they're actually pretty good at collecting (and by lack of reports to the contrary) securing this telemetry data. Where I using Windows, I'd probably let them have the data - though I'd be pretty pissed if off didn't mean off. (I'm kinda big on that - off is off and on is on, it's an honesty thing.)
One other thing to note... Since the days of 95, but more pronounced with 98, there tends to be a big swing in the direction of people who are moving to Linux. Six months or so later, they're gone from the forums and the .ISO download numbers are back to normal. In a year, they've turned into rabid supporters of the OS they were so against. I have been watching and expecting a huge swing in numbers. (I seed well over 100 distros - the last time I counted there were 144, it's not an exact metric so I also look at the sites that offer their stats like DistroWatch.)
You know what I've seen? Not a whole hell of a big jump in numbers. Lots of noise. I see a lot of that. But the numbers don't seem to indicate any huge swings, perhaps fewer now than when 8 and 8.1 dropped. I'd not be surprised if someone could get and crunch the numbers and they turned out that this uptake isn't all that high with Linux right now. So, people don't actually seem to be pissed off about this at the level where they're jumping ship.
I dunno... Were I still using Windows, this might have been enough to make me bail. It's not that I dislike the telemetry. It's that I want off when I say off. If I can't trust my OS to do that, what can I trust it for?
"So long and thanks for all the fish."
My computer phones home to Google thousands of times a day, too.
Funny thing is if you take an Android phone to China it'll self drain it's battery in attempts to phone home to Google. That's kind of the default action when you can see a network but didn't manage to get through to a server. Retry.
Thousands of connection attempts may drop down to a handful if the connections actually went through.
But then there's another question of does windows bulk store telemetry information, does it attempt to send it out blind, or did the user by dropping connections to Microsoft IPs stop windows from even attempting collect telemetry in the first place.
There was nothing right about this test.
I'm free to run a *nix box without ever connecting it to the internet. How long before Windows 10 times out and refuses to work unless it's re-validated (may be in a future update, may already exist ... but we know it's coming).
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
Those are connections *I* choose to initiate. That you don't see the difference is a bit scary.
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
When something phones home, and doesn't tell you what data it sends, why would you assume that it's not forwarding that info as well?
"Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
The DoD says DoD puters have to have EE and set telemetry to its lowest setting (EE only), so I am comfortable with it.
iase.disa.mil and search under operating systems.
Personally, I'm going to avoid win 10 until I can't, then run ReactOS. And anything that doesn't work in ReactOS will get a bug report and a simple example program. A simple main.c showing the problem gets good results, I have found.
If you have two apps which are exactly the same to start with and only one does analytics, it would crush the competitor in a year or two after all significant crashes are fixed and user interaction is optimized by studying flow between screens. People grumble about tracking but do not reflect that in their purchasing/web browsing decisions to the extent of choosing an inferior but more anonymous product.
The test results don't make sense, anyway. Wouldn't it be better to collect information into a log and then send that log once a day with a scheduler?
Who needs to worry about thousands of connections when only one is needed?
I woke up one morning to find my Windows 7 Laptop was attempting to run Windows 10 for the first time but crashed because my laptop wasn't compatible with Windows 10. If this installation were successful and I was upgraded without consent, how am I agreeing to their EULA? Before you could simply abort the installation and refuse to install the product if you didn't agree with the EULA. In my upgrade to Windows 10, I was never given the option to accept or decline the EULA license that came with Windows 10. I just woke up in the morning and realized while I was asleep my laptop was upgraded to Windows 10 but that the upgrade failed because my laptop wasn't compatible with Windows 10. I ended up having to wipe the entire hard drive and reinstall Windows 7 and recovered some of my previous files from backups I made. After this incident, I have chosen not to use Windows at all but still will have to use it for some tasks but the rest of my computers run Linux and I've been happy with Linux.