What a quality article, lol.
Voat user [...] News Sources: Forbes
That was the voat thread I saw last week some time, which I summarised my thoughts on r/netsec as
I hope he actually does some analysis of the traffic in future rather than just logging connections and speculating over what it is.
Install Glasswire, look at what processes/services are sending data where.
Set up a personal CA and MITM the TLS connections and actually see what data is being sent.
Then maybe there’ll be something interesting.
i.e. I laughed at his “analysis”
Citing Forbes as a source shows how blogspammy the entire post is.
has completed some extensive testing on Windows 10
(FFS this site adds those crappy backlinks to anything you copy, kill me now).
“Extensive”… He learned how to log connections on his router. See my comment above as to what I’d consider to be a starting point for analysis, what has been done is hardly extensive.
where he reports that during an 8-hour period, Windows 10 attempted to send back data from his PC to over 51 different IPS addresses owned by Microsoft, and at a staggering 5500 times.
Hey, actual content from the original source!
After 30 hours, the data being sent back to Microsoft from Windows 10 expanded to a huge 113 non-private IP addresses. These IP addresses being non-private means that hackers can intercept that data, which makes anyone using Windows 10 very, very vulnerable.
“non-private IP addresses” OooOoHhh… What a bunch of FUD.
First-up any sensitive data would be transferred using TLS, and because the guy doing the “analysis” hasn’t yet learned how to look at the traffic he’s logged (Or maybe it was of such little value he intentionally left it out) he hasn’t even figured out what the un-encrypted traffic is. NCSI and Windows updates use HTTP, the UDP traffic is Teredo, I’m sure some of the default start menu tiles also load data (Where else does it get weather and news from?).
The testing was repeated on another Windows 10 clean installation with all of the data tracking options completely disabled, and third-party tool DisableWinTracking was installed, which attempts to shut down all of the hidden Windows 10 data reporting attempts. This didn't help, as at the end of the 30-hour period, Windows 10 had still pushed data to Microsoft 2758 times, across 30 different IP addresses.
Confirmation bias at it’s finest.
“The computer is establishing 2500 less connections, obviously this means Microsoft are still stealing all muh TV shows”