Live data from Hacker News

HTML over DNS: Serving Blog Content over DNS

jacobkiers.net

71–77 of 77 posts

Re: HTML over DNS: Serving Blog Content over DNS

#71
post #28

Earlier quoted context omitted.

Packet size is a really good detection for this. DNS packets should only be so big ;)

So I split my packets up into smaller chunks. Now you need to rate limit DNS. But you still need to allow regular DNS traffic somehow, or you break the internet.

Well, allowlist to a known DNS server and block anything on DNS that isn't allowlisted.

Re: HTML over DNS: Serving Blog Content over DNS

#72
post #56

Earlier quoted context omitted.

> but once they turn it on it should have relatively good feature support How could they even know to tuen it on when all they get is an empty page?

They are used to it? The number of users who have JS disabled is already small. The number of those users who lack the technical expertise to enable it as needed (and understand when that is necessary — e.g. with a blank or broken page) is probably many, many times smaller.

> They are used to it?

And yet most site designers which require javascript turn out to be thoughtful enough to make a note of it rather than leave a completely empty page.

And public sites which absolutely require javascript to do anything turn out to be quite rare.

So there’s no reason to be used to it. “Some buttons don’t work”, yes I do expect i need to allow some JS. “Nothing shows up at all” is usually a network issue.

Re: HTML over DNS: Serving Blog Content over DNS

#73
post #71

Earlier quoted context omitted.

So I split my packets up into smaller chunks. Now you need to rate limit DNS. But you still need to allow regular DNS traffic somehow, or you break the internet.

Well, allowlist to a known DNS server and block anything on DNS that isn't allowlisted.

The exfiltrated data isn't for DNS resolvers but is leaked to Nameservers through them.

A similar technique forms the basis of how services like dnsleaktest.com and which.nameserve.rs identify DNS resolvers in-use by a particular client.

Re: HTML over DNS: Serving Blog Content over DNS

#75
post #51

Earlier quoted context omitted.

Yes. I recently wrote a Lua-scriptable DNS server called redns[1] (which seems to be a pretty popular name for hobbyist DNS servers, BTW) only to test some of those attacks. [1] https://github.com/luismedel/redns

Nice! Whenever I see regexs hanging off the Internet, my heart skips a beat! :)

Thanks!

To be fair, I hope nobody, never, ever use my server in a production environment :-)

Re: HTML over DNS: Serving Blog Content over DNS

#76
That's interesting. I'm thinking about ways how this could be combined with https://dnskv.com - which allows not only reading from dns, but also storing:

    dig TXT content.uniquekey.dnskv.com
    --> 'ok'

    dig TXT uniquekey.dnskv.com
    --> 'content'
Only thing that comes to my mind is data exfiltration from sites with content-security-policy which for some reason allows some DoH site

Re: HTML over DNS: Serving Blog Content over DNS

#77
post #51

Earlier quoted context omitted.

Nice! Whenever I see regexs hanging off the Internet, my heart skips a beat! :)

Thanks! To be fair, I hope nobody, never, ever use my server in a production environment :-)

It looks pretty useful to me (for tests).

But, with software..... Build it and they will use it! :)

Post reply on HN