3 ms·
"I'm still trying to imagine the way one exploits a lack of partitioning in the DNS cache." There's a PDF here: https://www.ndss-symposium.org/wp-content/uploa
by tyingq 6y ago
"I'm still trying to imagine the way one exploits a lack of partitioning in the DNS cache."
There's a PDF here: https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_04B-4_Klein_paper.pdf https://www.ndss-symposium.org/wp-content/uploads/2019/02/nd...
Basically timing based. See https://www.audero.it/demo/resource-timing-api-demo.html https://www.audero.it/demo/resource-timing-api-demo.html for a demo of what's available in the browser's navigation and resource timing API. For example, I get this on a cached reload:
domainLookupStart: 52.090000128373504
domainLookupEnd: 52.090000128373504
The PDF explains some enhancements that make it more reliable, like publishing multiple A records and watching order, etc. Also, the demo link isn't really showing what you would do...the resource being downloaded would be marked as non-cacheable so that you would be measuring "DNS lookup was cached or not" instead of "Entire Asset was cached, therefore no DNS lookup happened".
- nixpulvis 6y agoIt's always timing isn't it... Thanks for those links.