Nvidia Adds Telemetry To Latest Drivers

I like to point out, who is interested in blocking harmful and undesired domains with the help of hosts files, there is, in my opinion, a very good source for that. It's a repository which extends and
consolidates existing hosts files from other sites, and merges them into a unified hosts file with duplicates removed. There are hosts files ready to download to choose from by category (adware, malware, gambling, porn, social, or in combination). Even one can generate a own, tailored unified hosts file by adding extra sources.

Unified hosts files blocking unique domains from 29,749 to 35,992 at the time of this writing.

https://github.com/StevenBlack/hosts
 
I like to point out, who is interested in blocking harmful and undesired domains with the help of hosts files, there is, in my opinion, a very good source for that. It's a repository which extends and
consolidates existing hosts files from other sites, and merges them into a unified hosts file with duplicates removed. There are hosts files ready to download to choose from by category (adware, malware, gambling, porn, social, or in combination). Even one can generate a own, tailored unified hosts file by adding extra sources.

Unified hosts files blocking unique domains from 29,749 to 35,992 at the time of this writing.

https://github.com/StevenBlack/hosts

This seems a good one. With the other ones I still get ads, so I'll try this one for a while. Also, FF uses around 120MB less memory without AdblockPlus on my system.
 
At the moment I'm using adblock to block all ads and trackers. Does the hosts file method has any advantages over that?

I put the tools that I use for DNS filtering with unbound(8) on GitHub -- https://github.com/cyclaero/void-zones-tools. The README file discusses the pros & cons of the various methods and there is also a section on "How does this compare to Browser Plugins?"

...
  1. Browser plugins are destined to one piece of software and not to the whole machine. Void zones are active for the whole machine or in the case of a gateway, for any number of clients, and even for those (Android) which don't allow ad-blocking plugins.

  2. Browser plugins are active filters, that means, beside the advertised behaviour, they are able to do something in the background. This is a matter of trust, which may sometimes miserably trapped -- see the WoT incident. Void zones are passive. The actual filtering is done by the DNS resolver, here *Unbound*, which is much less likely of doing undesired things behind your back.
...
 
I like to point out, who is interested in blocking harmful and undesired domains with the help of hosts files, there is, in my opinion, a very good source for that. It's a repository which extends and
consolidates existing hosts files from other sites, and merges them into a unified hosts file with duplicates removed. There are hosts files ready to download to choose from by category (adware, malware, gambling, porn, social, or in combination). Even one can generate a own, tailored unified hosts file by adding extra sources.

Unified hosts files blocking unique domains from 29,749 to 35,992 at the time of this writing.

https://github.com/StevenBlack/hosts

Nice compilation, I am trying the Window 10 telemetry list from that repository with my void-zones-tools for some days, and I will add it to my void-zones-update.sh script when this won't disturb the desired operation of my 2 Windows 10 clients.
 
This looks really interesting. Why isn't this in ports? ;)
The usual excuse for laziness. I thought nobody would like it.
First I'll have to dive into unbound(1) for this.
Two years ago, I described the method including setting-up Unbound in two posts on my BLog. This is in German language, however, using an online translation tool, perhaps it might be still suitable to get you started:

http://blog.obsigna.net/?p=504
http://blog.obsigna.net/?p=509

PS: The tools presented in the 2 years old BLog posts still do work, however, I suggest to use the updated ones on GitHub.
 
My german isn't bad (I'm from NL) so I'll read and try to understand the german text first.
 
The usual excuse for laziness. I thought nobody would like it.
I have been looking for something that would do what what you are doing here, namely the blocking all subdomains of a domain.

One question, say I wanted to block just the ads on a domain will just entering something like:
0.0.0.0 ads.exampledomain.com

block just that but allow www.exampledomain.com, or is my understanding incorrect?
 
I have been looking for something that would do what what you are doing here, namely the blocking all subdomains of a domain.

One question, say I wanted to block just the ads on a domain will just entering something like:
0.0.0.0 ads.exampledomain.com

block just that but allow www.exampledomain.com, or is my understanding incorrect?

Your understanding is correct. Once the tool hosts2zones converted this to an empty (void) Unbound zone entry ...
Code:
local-zone: "ads.exampledomain.com" static
... Unbound would respond with NXDOMAIN for requests to ads.exampledomain.com itself and all of its subdomains, but, it would process requests to www.exampledomain.com normally, i.e. either forward or recursively resolve it.

Perhaps you already realized it, anyway it is good to emphasize it again. The tool hosts2zones does join subdomain host entries into one zone for the highest common level domain. By this way the number of void-zones are significantly reduced. For example, today's run of void-zones-update.sh turned 26849 hosts file entries into 17648 void zones.
 
The usual excuse for laziness. I thought nobody would like it.

Two years ago, I described the method including setting-up Unbound in two posts on my BLog. This is in German language, however, using an online translation tool, perhaps it might be still suitable to get you started:

http://blog.obsigna.net/?p=504
http://blog.obsigna.net/?p=509

PS: The tools presented in the 2 years old BLog posts still do work, however, I suggest to use the updated ones on GitHub.

Unbound is running and working. Trying to install a working /var/unbound/local-void.zones now. I've followed the directions on your site http://blog.obsigna.net/?p=509 but the binary hosts2zones coredumps with an "illegal instruction".
 
Unbound is running and working. Trying to install a working /var/unbound/local-void.zones now. I've followed the directions on your site http://blog.obsigna.net/?p=509 but the binary hosts2zones coredumps with an "illegal instruction".
Did you use the software from 2014 from my BLog post or are your referring to the updated one on GitHub?

PS: just checked the tool from 2014 and it compiled and worked fine on my machine FreeBSD 11.0-RELEASE-p3, amd64, Intel(R) Atom(TM) CPU D510 @ 1.66GHz (1666.72-MHz K8-class CPU)
 
Ah, sorry my fault. Got the wrong one from 2014. I'll try the one from github. But do I have to install github first? The command "git" doesn't work out of the box.
 
You can fetch the .zip-archive of the repository.
fetch -o void-zones-tools-master.zip https://github.com/cyclaero/void-zones-tools/archive/master.zip
unzip void-zones-tools-master.zip

However, I find it still strange that the "old" tool crashes on your machine. If the new one crashes as well, then please make the tool with the command make clean install CDEFS="-march=native", and then try again.
 
New tool crashes as well. The directory /usr/local/etc/void-zones is created and filled with the hosts files. However /var/unbound/local-void.zones is still empty and the binary coredumps with an illegal instruction.
...And same with make clean install CDEFS="-march=native"
 
New tool crashes as well. The directory /usr/local/etc/void-zones is created and filled with the hosts files. However /var/unbound/local-void.zones is still empty and the binary coredumps with an illegal instruction.
...And same with make clean install CDEFS="-march=native"
Please can you post some details of your machine? Which FreeBSD version (32 or 64bit) and which CPU?
Please can you edit the Makefile, changing the CFLAGS -g0 to g and -Ofast to -O0. Then make install and run again. Then it would be great if you could upload the coredump to somewhere where I can pick it up.
 
Sure I have a dual Xeon 2.8 GHz (Nocona) with 4 GB RAM. Uname -a: FreeBSD yokozuna.lan 11.0-STABLE FreeBSD 11.0-STABLE #0 r307320: Fri Oct 14 21:19:48 CEST 2016 root@yokozuna.lan:/usr/obj/usr/src/sys/YOKOZUNA amd64. I try the Makefile edit.
 
I received and analyzed the core dump. For some reasons, your Xeon does not like one or some SSE instructions. So, for the time being it will help to disable it.

Please edit the file binutils.h. On line 151 please replace #if defined(__x86_64__) with #if 0. By this way all functions using SSE will be disabled and the non-vector versions will be used instead. Build & install again, and now it should work.

make clean install

I need to investigate why the Xeon got a problem with some SSE instructions.
 
Compiling and running went fine now. Got a new error though:
Code:
# service local_unbound restart
Stopping local_unbound.
Waiting for PIDS: 87910.
Starting local_unbound.
/var/unbound/local-void.zones:1: error: syntax error
read /var/unbound/unbound.conf failed: 1 errors in configuration file
[1478906271] unbound[87948:0] fatal error: Could not read config file: /var/unbound/unbound.conf
/etc/rc.d/local_unbound: WARNING: failed to start local_unbound
 
Please show your file /var/unbound/unbound.conf and please send me the generated file /var/unbound/local-void.zones by the same way like you send to me the core dump.
 
The generated file /var/unbound/local-void.zones was OK.

I experimented a little bit with your file unbound.conf, and I found out that any local-zone: directive must come before the forward-zone: directives that are included by the file /var/unbound/forward.conf. So please move the include directive of /var/unbound/local-void.zones before all the other includes. The following did not error out:

Code:
server:
        username: unbound
        directory: /var/unbound
        chroot: /var/unbound
        pidfile: /var/run/local_unbound.pid
        auto-trust-anchor-file: /var/unbound/root.key

include: /var/unbound/local-void.zones
include: /var/unbound/forward.conf
include: /var/unbound/lan-zones.conf
include: /var/unbound/control.conf
include: /var/unbound/conf.d/*.conf
 
Yes, and we have liftoff! Thanks for all your help. FF is faster and uses a lot less memory so this is a really nice tool. Some ads are still coming through but that's a matter of updating the list.

Another thing I'll have to do is learn a bit about DNS, the only site so far that is unreachable after running unbound is my cloud storage in FF.
 
Just in regards of browser add on, there is uBlock Origin what include everything AdBlock include and a lot of more.
You cannot beat telemetry of any kind of software, let it be the driver package of NVIDIA, or the various calling home daemons in Windows 10, or of software on other devices in your home network (Smart TVs, Playstations, Printers, ..., zillions of IoT devices ante porta) with just another browser plugin -- not with the very best of the world.

I am sure that filtering at the DNS (with a Hosts file or by the way of void zones) + perhaps some blocking at the Firewall is much more promising for dealing with the issue which was risen in the present thread.
 
Back
Top