This is a big privacy concern with AdGuardHome as well because they will ask the upstream DNS (and possibly your ISP) you are using for information about the IPV6 address using WHOIS. I believe there is away to disable the WHOIS approach, but you need to edit the .yaml file. I recommend looking at their wiki carefully before deciding to do such.
Thanks for the info. I put AdGuard on hold for a bit as I am trying to work out some IPv6 issues in order to get the name resolution I desire. I've seen something in the issue tracker about privacy concerns, but I'm not entirely sure they are warranted. If you are using GUAs in your environment, the idea is they are publicly routable anyway - so there should not be a concern if those are made visible to the outside.
It seems the concern should only be with stateless/SLAAC addressing when privacy extensions are not enabled. In which case a device's MAC might get leaked. Or perhaps the concern is simply tracking based on IP - whereas with IPv4 and NAT you simply know that the device is originating from the single public IP, here you know the specific GUA accessing. I wrote my observations up here:
Hello, in my configuration I am using Adguard home with unbound. the network setup is following: Router/Gateway is an Fritz!Box with DHCP for IPv4 and IPv6 FritzBox is providing via DHCP the the IP...
github.com
I'm interested in specifically how you judge this as a privacy concern? Of course I agree that the WHOIS approach should be able to be disabled if you choose not to use it. I could not find anything about doing this, but I assume (since you reference the YAML) that the appropriate section is:
Code:
clients:
runtime_sources:
whois: true
arp: true
rdns: true
dhcp: true
hosts: true
Because I could not find anything about it, I don't know what the danger is of disabling WHOIS. I think the only time having WHOIS might be useful is if you are running a publicly accessible AdGuard server and accessing it from outside your network where an incoming client might not be registered. However since it is unlikely that another external client has a PTR record, it seems the best you are going to get with WHOIS is an OrgName. I suppose that's better than nothing, but it's not much
I am going to be removing the apache code pretty soon, however the bcrypt and python distributions are for generating the encrypted password for AdGuardHome. The Go packages are only installed to provide the same thing, if python fails to install or unavailable in entware for that particular architecture. Originally I used htpasswd from apache-utils to generate the password. However this installed apache on peoples routers (big security problem if your not actually using it correctly). The installer only uninstalls apache if it was originally used to install it (on the next update I will probably remove this). So, I switched to installing bcrypt through python packaging ( or alternatively through Go if python doesn't work). All of this is to generate the encrypted password for users to log into AdGuardHome WebUI (and change the password through the installer whenever they like).
Good to know. I have some concerns about the additional packages mostly because I have some other outside constraints (which I won't detail here) about the Entware install getting too large, but I don't actually know if this will be a problem or not for me.
I wasn't personally worried about Apache - because I'm not using it - I was just concerned on my first quick glance through of the code base that I saw it was getting removed.
What mechanism do/can you use to ensure that Apache only gets removed if it was installed by the installer itself?