mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
Additional validation in $dnsrewrite rules #2307
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#2307
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ainar-g on GitHub (Dec 28, 2020).
Originally assigned to: @ainar-g on GitHub.
Context: #2101, #2452, #2492.
We need to decide, which additional validations we want for the
$dnsrewriteresponse modifier. Among the ones that are likely to be requested:MXandPTRrewrites.CNAMErewrites.SVCB/HTTPSrewrites.Any more I've missed?
@DandelionSprout commented on GitHub (Jan 12, 2021):
Presuming I understand the question correctly: I get quite a few
TXTDNS requests to my server, e.g.hostname.bind,id.server,version.bind, etc. For those, they can be treated as hostnames, but without being limited to regular TLDs.There's also
RRSIGrequests (to e.g.pizzaseo.com), which I doubt the legitimacy of as a whole. If they are to be treated as legitimate requests, then the hostname is sufficient.@ainar-g commented on GitHub (Jan 13, 2021):
@DandelionSprout
If I recall correctly,
TXTrecords can contain arbitrary textual data, so I don't think we'll apply any validations there besides the byte size.As for
RRSIGrecords, we currently don't support them. If you have a need for them, please file a separate issue about it and we'll try to add them in v0.106.0 as well.