-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unauthorized clients accessing DNS-overTLS #6890
Comments
Hi @tescophil, thanks for the report. Could you please tell me more about how you have AdGuard Home setup? Reproducing the issue with verbose logs enabled may also show us more of the picture. |
Hi, So I've already given you my authorised clients settings so I dont really see how a screenshot will help, but... I'm setup on a standalone intel machine (not a VM) and have had the same setup for years. I provide an external (public) DNS-over-TLS for personal Android and iOS devices via port 853, all of which have individual ClientID to control access (which is now broken). The unauthorised clients are colored red in the client list, however it's not clear what this actually means and looking in the log all these queries are answered and not blocked/ignored as they should be. I can get you my yaml settings, but I'm currently on a bus in Malta, so it will have to be later on this evening. |
I have the same problem as @tescophil. |
OK here is my yaml config (think I've removed all personal info from this..)
|
I can reproduce. Seems to only affect encrypted protos. Will fix today. |
Can confirm with latest stable, using encrypted DNS only. |
List is 404. |
@tescophil, @kashikoy, @rs-com, we've just published v0.107.48, which should fix this. Can you please update and recheck? |
Looks good to me 👍 |
Yes it works, thank you ! |
These both below are the same:
If you have the Lite version, you don't need the mini. If Lite is too harsh for your taste, downgrade to mini.
Same thing down here. Everything from Multi is inside the Pro version.
|
Is it possible to list allowed clients by hostname?! For example when client come from telekom.de, they have hostname like D31GEA.telekom.com, so i would like to allow telekom.de clients as a wildcard. How could this be done? |
It's simpler to add the ASN, but it's only available on adguard-dns.io unfurtunately... Get the IPs from ASN of Telekom Deutschland and add it to the access list. https://www.peeringdb.com/asn/3320 and the IP List: Put in 3320 |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
GitHub releases or script from README
Setup
On one machine
AdGuard Home version
v0.107.47
Action
Since installing this latest version I see DNS-over-TLS queries from unauthorised clients being answered.
I have defined a list of authorised clients which include local private IP ranges for my local network and a number of client tags/labels for remote clients.
All the answered 'unauthorised' queries were from IP ranges outside the ones defined in the authorised clients list and non of the requests used ID tag URL's.
This is the list of authorised IP ranges
127.0.0.1
10.8.1.0/24
192.168.0.0/24
192.168.10.0/24
192.168.20.0/24
192.168.30.0/24
192.168.40.0/24
plus several ClientID,'s
Expected result
I don't expect to see any DNS-over-TLS queries answered for unauthorised clients.
Actual result
External queries from unauthorised clients are being answered when they should be dropped.
I see this as a BIG security problem....
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: