How to block in Windows10 Telemetry with pfsense
-
Thank God I already switched my machines to Linux.
I've been contemplating that for 10+ years, but there was always a reliance on special software that I couldn't get for Linux. Now that I don't do a lot of desktop stuff at home anymore, I'm thinking now might be the time to dump Win10 and go with Mint Cinnamon.
-
You can find equivalent programs under Linux for most of the daily tasks. No to little effort is required to switch over.
There could be though very special industrial apps which were made for Windows-only, that's true. But for the regular home user, Linux is a perfect alternative. -
I've been adminning Linux boxes for more than a decade so I'm generally aware of what's available. For me, the showstoppers were always a decent money-management app (eg. Quicken, MS Money), a good Usenet browser (eg. Newsleecher, Forte Agent) and a decent RSS reader (eg. Feeddemon, QuiteRSS). Nowadays I don't use a money app, Usenet indexers have removed the need for an NNTP browser, and there are several decent RSS readers for Linux. I really should have thought of this 2 weeks ago before I spent a weekend doing the Windows 10 thing.
-
@KOM:
A centralized solution would be best. If you're going to go local, why not just use one of the many utils already out there?
http://www.oo-software.com/en/shutup10
http://pxc-coding.com/portfolio/donotspy10/
Do not use that, you cannot go back without using a " restore point".
-
have a look here:
https://github.com/WindowsLies/BlockWindows
http://www.ghacks.net/2015/08/28/microsoft-intensifies-data-collection-on-windows-7-and-8-systems/
-
Do not use that, you cannot go back without using a " restore point".
ShutUp10 will prompt you to let it create one before it applies its changes. I didn't bother as I can't see any scenario where I would need to undo that stuff.
-
Please forgive me. I'm a bit of a noob. Do these look right?
 -
yes it looks ok.
-
Your pass rule isn't required unless you've really locked down your LAN. By default, LAN has full access out to everywhere.
-
yes it is required because other way update destinations will be blocked from Blocked rule that have these destinations included in case you don't want to allow update.
-
yes it is required because other way update destinations will be blocked from Blocked rule that have these destinations included in case you don't want to allow update.
Huh? Windows Update domains shouldn't be included in your telemetry alias.
-
some people want to block everyhing because MS can deliver an "security update" that will install telemetry and also use update hosts to get data from computer so this way is better, at least for me to have updates (allow only updates-block everything).
-
I still don't see how this is a good solution. Are you literally whitelisting every destination address you want access to and blocking everything else on the Internet? Because MS can spin up a zillion new domains on a whim.
-
MS can do whatever they want, but they must be able to make your computer to talk with any new domains ( and they can do this only with an allowed to install update ).
If now you block the telemetry C&C servers, there is no other way your computer will know to talk with new domains until you will install that update.This is what we have for now, if we have another better way please elaborate ( except unplug the cable, stop using MS OS… ).
-
yes it looks ok.
It's not ok as per your description, because it's a pass rule, not a block rule.
-
@KOM:
yes it is required because other way update destinations will be blocked from Blocked rule that have these destinations included in case you don't want to allow update.
Huh? Windows Update domains shouldn't be included in your telemetry alias.
Which are the Windows Update domains, btw?
I found these:
windowsupdate.microsoft.com update.microsoft.com windowsupdate.com download.windowsupdate.com wustat.windows.com ntservicepack.microsoft.comAre there any others?
-
-
Setup a WSUS server, whitelist that to talk to Microsoft, and block all clients?
I'm torn between Linux and FreeBSD. Linux has better Steam support, but a lot of stuff is being done in FreeBSD to increase comparability. ZFS and Jails are very attractive, even on a desktop.
-
Whenever I have the choice, M$-shyt has been replaced by opensuse or PC-BSD (the later has a steeper learning curve and is not so well supported, but is free of systemd). Big plus: you can both run with KDE desktop, which made it much easier to switch between these two, and btw the handling is not sooo far away from Windows xp/7…
-
PS: Here
http://techne.alaya.net/?p=12499
you can find a long list of IPs and host names to block for Windows telemetry.
