You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a way to specify addresses that should not be anonymized or modified. This would have to be a list. For an authoritative name server we would specify the server's addresses here. This might be a significant amount of code change.
If both ports are dns_port then both addresses get anonymized.
Existing behavior, but with a warning or error. A command line option should specify if the condition is fatal and causes the program to exit.
jelu
added a commit
to jelu/dnscap
that referenced
this issue
Jan 23, 2023
- anon plugins: Issue DNS-OARC#276: When anonymizing clients, anonymize both source and destination if they are both using the masking port since it can't be determined who's the client and who's the server
jelu
changed the title
In anonymization plugins, determining client vs server by port can lead to unanonymized packets.
In anonymization plugins, specify addresses that should not be anonymized or modified
Jan 23, 2023
I'm skipping warning/fatal, think it's more important to not leak addresses so the fix will be released soon and the list option can be implemented later.
In anonymization plugins, determining client vs server by port can lead to unanonymized packets.
For example, this code:
means that if only_clients is set (-c option) and a query comes from source port 53, the source IP address will not be anonymized.
The text was updated successfully, but these errors were encountered: