Interesting spy service to block

In article
emailer.net
Fritz Wuehler fritz@spamexpire-
201603.rodent.frell.theremailer.net wrote:

found this at https://github.com/RMerl/asuswrt-mer...ki/Using-ipset

ipset -N MicrosoftSpyServers iphash
for IP in 23.99.10.11 63.85.36.35 63.85.36.50 64.4.6.100 64.4.54.22 64.4.54.32 64.4.54.254 \
65.52.100.7 65.52.100.9 65.52.100.11 65.52.100.91 65.52.100.92 65.52.100.93 65.52.100.94 \
65.55.29.238 65.55.39.10 65.55.44.108 65.55.163.222 65.55.252.43 65.55.252.63 65.55.252.71 \
65.55.252.92 65.55.252.93 66.119.144.157 93.184.215.200 104.76.146.123 111.221.29.177 \
131.107.113.238 131.253.40.37 134.170.52.151 134.170.58.190 134.170.115.60 134.170.115.62 \
134.170.188.248 157.55.129.21 157.55.133.204 157.56.91.77 168.62.187.13 191.234.72.183 \
191.234.72.186 191.234.72.188 191.234.72.190 204.79.197.200 207.46.223.94 207.68.166.254
do
ipset -A MicrosoftSpyServers $IP
done


God help us if you are the geniuses behind this latest linux
silliness.

1. You can't block the MS telemetry connections doing this.
I'm not going to tell you why or how they get around it.

2. "Blocking" some of those IP addresses results in elevated
CPU and resource usage as the OS works to get around your
archaic blocking attempts - and it will.

3. MS thought the telemetry reporting out very well. It IS
possible to neuter it, but you have to understand the product in
a modern sense and not the Windows 98 approach that is being
used to attack it. Those days are over.

4. The answers are on the MS website. They did not hide
anything. The consumer version of OS is harder to neuter than
the others. If you can read, you can find the solutions.

On 03/30/16 06:29, Cornelis Tromp so wittily quipped:
In article
emailer.net
Fritz Wuehler fritz@spamexpire-
201603.rodent.frell.theremailer.net wrote:


found this at https://github.com/RMerl/asuswrt-mer...ki/Using-ipset

ipset -N MicrosoftSpyServers iphash
for IP in 23.99.10.11 63.85.36.35 63.85.36.50 64.4.6.100 64.4.54.22 64.4.54.32 64.4.54.254 \
65.52.100.7 65.52.100.9 65.52.100.11 65.52.100.91 65.52.100.92 65.52.100.93 65.52.100.94 \
65.55.29.238 65.55.39.10 65.55.44.108 65.55.163.222 65.55.252.43 65.55.252.63 65.55.252.71 \
65.55.252.92 65.55.252.93 66.119.144.157 93.184.215.200 104.76.146.123 111.221.29.177 \
131.107.113.238 131.253.40.37 134.170.52.151 134.170.58.190 134.170.115.60 134.170.115.62 \
134.170.188.248 157.55.129.21 157.55.133.204 157.56.91.77 168.62.187.13 191.234.72.183 \
191.234.72.186 191.234.72.188 191.234.72.190 204.79.197.200 207.46.223.94 207.68.166.254
do
ipset -A MicrosoftSpyServers $IP
done


God help us if you are the geniuses behind this latest linux
silliness.

1. You can't block the MS telemetry connections doing this.
I'm not going to tell you why or how they get around it.

2. "Blocking" some of those IP addresses results in elevated
CPU and resource usage as the OS works to get around your
archaic blocking attempts - and it will.

Using ipset will bring the CPU and resource usage to almost nothing.

3. MS thought the telemetry reporting out very well. It IS
possible to neuter it, but you have to understand the product in
a modern sense and not the Windows 98 approach that is being
used to attack it. Those days are over.

4. The answers are on the MS website. They did not hide
anything. The consumer version of OS is harder to neuter than
the others. If you can read, you can find the solutions.

In other words, he is saying to just lie down and die. You don't have any chance to defeat MS and it is futile to try. If this guy had been a commander in any of our wars, we would have been quickly defeated.


having control over firewall settings in a non-windows router (most wifi
routers have their own firewalls to block at the IP address level) can
let you do something similar.

interesting IP address list, though.

I've read that if you're not careful with the IP blocking, license
validation expires over a period time, 30 days maybe, and you might have
to use a phone to re-activate windows 10. Maybe someone can confirm this?