Proceedings of the 15th ACM Conference on Computer and Communications Security 2008
DOI: 10.1145/1455770.1455798
|View full text |Cite
|
Sign up to set email alerts
|

Increased DNS forgery resistance through 0x20-bit encoding

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
80
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 75 publications
(80 citation statements)
references
References 13 publications
0
80
0
Order By: Relevance
“…A number of recently proposed defenses against DNS cache poisoning, including source port randomization, 0x20-bit encoding, XQID, and WSEC-DNS, fundamentally depend on the asymmetric accessibility of the components used for authenticating responses to DNS queries [7,8,11,20].…”
Section: Response Forgery Using Eavesdroppingmentioning
confidence: 99%
See 1 more Smart Citation
“…A number of recently proposed defenses against DNS cache poisoning, including source port randomization, 0x20-bit encoding, XQID, and WSEC-DNS, fundamentally depend on the asymmetric accessibility of the components used for authenticating responses to DNS queries [7,8,11,20].…”
Section: Response Forgery Using Eavesdroppingmentioning
confidence: 99%
“…This patch depends on the configuration of the local network such as the firewall imposing strict constraints on inbound connections. Other solutions aiming to prevent blind response forgery by increasing entropy of queries are 0x20-bit encoding [7], which randomizes capitalization of letters in the query (the amount of entropy depends on the length of the query), and WSEC-DNS [20] and XQID [11], which use a challenge-response scheme with random nonces.…”
Section: Defensesmentioning
confidence: 99%
“…6 We then query the ODNS for the google.com subdomain and determine 3 We require at least ten transactions for the results in this paper, but in other experiments we find the insights are not sensitive to the exact threshold. 4 We conclude that resolvers do not use static, incrementing, or decrementing transactions IDs by observing a high standard deviation in the transaction ID sequence. 5 Our results may be a lower bound on the adoption of 0x20 encoding as at least one major RDNS pool-Google Public DNS [8]-uses 0x20 encoding on a white-listed set of domains.…”
Section: Bailiwick Rules Violationsmentioning
confidence: 77%
“…While randomizing only the DNS transaction ID is insufficient protection, randomizing both values is an effective strategy [10]. Another technique to increasing entropy is "0x20 encoding" [4] in which the RDNS randomly changes the capitalization throughout query strings. Authoritative servers should be case insensitive when resolving the query yet retain the capitalization in their response [12].…”
Section: Kaminsky's Attackmentioning
confidence: 99%
See 1 more Smart Citation