adulau/pdns-qof
1
0
Fork 0
mirror of https://github.com/adulau/pdns-qof.git synced 2024-11-22 18:17:04 +00:00
Code Issues Projects Releases Packages Wiki Activity

typos, formatting

Browse source
This commit is contained in:
Aaron Kaplan 2013-12-25 19:56:45 +01:00
parent 85c5dd6c5b
commit f1af96418b
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
i-d/pdns-qof.txt
View file

@ -362,7 +362,7 @@ Internet-Draft Passive DNS - Common Output Format December 2013
DNS recursors. In this process, they intentionally omit the source DNS recursors. In this process, they intentionally omit the source
IP, source port, destination IP and destination port. Furthermore, IP, source port, destination IP and destination port. Furthermore,
since multiple sensors feed into a passive DNS server, the resulting since multiple sensors feed into a passive DNS server, the resulting
data gets mixed together, reducing the likelyhood that Passive DNS data gets mixed together, reducing the likelihood that Passive DNS
Servers are able to find out much about the actual person querying Servers are able to find out much about the actual person querying
the DNS records nor who actually sent the query. In this sense, the DNS records nor who actually sent the query. In this sense,
passive DNS Servers are similar to keeping an archive of all previous passive DNS Servers are similar to keeping an archive of all previous

2
i-d/pdns-qof.xml
View file

@ -270,7 +270,7 @@ CR = %x0D
</section> </section>
<section anchor="Privacy" title="Privacy Considerations"> <section anchor="Privacy" title="Privacy Considerations">
<t>Passive DNS Servers collect DNS answers from multiple collecting points ("sensors") which are located on the Internet-facing side of DNS recursors. In this process, they intentionally omit the source IP, source port, destination IP and destination port. Furthermore, since multiple sensors feed into a passive DNS server, the resulting data gets mixed together, reducing the likelyhood that Passive DNS Servers are able to find out much about the actual person querying the DNS records nor who actually sent the query. In this sense, passive DNS Servers are similar to keeping an archive of all previous phone books -- if public DNS records can be compared to phone numbers, as they often are. <t>Passive DNS Servers collect DNS answers from multiple collecting points ("sensors") which are located on the Internet-facing side of DNS recursors. In this process, they intentionally omit the source IP, source port, destination IP and destination port. Furthermore, since multiple sensors feed into a passive DNS server, the resulting data gets mixed together, reducing the likelihood that Passive DNS Servers are able to find out much about the actual person querying the DNS records nor who actually sent the query. In this sense, passive DNS Servers are similar to keeping an archive of all previous phone books - if public DNS records can be compared to phone numbers - as they often are.
Nevertheless, the authors encourage Passive DNS implementors to take special care of privacy issues. <!-- FIXME: add reference / link --> draft-bortzmeyer-dnsop-dns-privacy-01.txt is an excellent starting point for this. Nevertheless, the authors encourage Passive DNS implementors to take special care of privacy issues. <!-- FIXME: add reference / link --> draft-bortzmeyer-dnsop-dns-privacy-01.txt is an excellent starting point for this.