Warning: this page links to (loud!) automatic playing audio.
TXT Record XSS
141–150 of 236 posts
Re: TXT Record XSS
#142Earlier quoted context omitted.
For another fantastic abuse of DNS, the Iodine* project uses DNS to tunnel IP which is just obscene. http://code.kryo.se/iodine/ (Why? Lots of captive portal wifi hotspots (think hotel/train etc) seem to allow DNS resolutions before stopping your other traffic.) * DNS uses port 53 which is the same as the atomic number for Iodine ;)
Ah, iodine. I've used it in airports, hotels, cafes - it's great. The only drawback is that it's slower than dialup and latency is off the charts. But when you're stuck on a cruise ship and internet access is $8 a minute, being able to ssh somewhere and browse the web and check your mail very slowly through links is worth it.
I usually just spoof mac addresses of people who already paid in most of those cases, the caveat usually being somebody had to pay.
Re: TXT Record XSS
#143I added FartScroll.js from the Onion to my text records: http://dig.whois.com.au/dig.php?dom=philipithomas.com&type=A...
:-) Thanks for this
Re: TXT Record XSS
#144A while ago I experimented with adding stuff to the version.bind field in bind. Just updated it:
mike@glue:~$ dig +short chaos txt version.bind @198.211.125.252
""
I put this in my named.conf:
version "";
This site is vulnerable:
http://dnscheck.pingdom.com/?domain=grepular.com
Although takes a minute before it kicks in. I did report it to them at the time, but never got a response.
Re: TXT Record XSS
#145Earlier quoted context omitted.
Ah, iodine. I've used it in airports, hotels, cafes - it's great. The only drawback is that it's slower than dialup and latency is off the charts. But when you're stuck on a cruise ship and internet access is $8 a minute, being able to ssh somewhere and browse the web and check your mail very slowly through links is worth it.
I usually just spoof mac addresses of people who already paid in most of those cases, the caveat usually being somebody had to pay.
If those people have a download limit that's rather unscrupulous.
Re: TXT Record XSS
#146Earlier quoted context omitted.
I don't know how things work now, but at least a few years ago there were plenty of DNS server that would take basically the full 48hours to update, regardless of TTL.
I think the rise of no-fixed-IP load balancers like Amazon ELB has dramatically reduced that.
Aren't the IPs of the load balancers more or less fixed, though?
Re: TXT Record XSS
#147Earlier quoted context omitted.
dam, that got downvoted into oblivion haha. honest question... although i dont believe it should be, a third party injecting javascript to demonstrate an exploit might be...
He hasn't injected anything. It's just his public DNS record that this page has chosen to display without sanitizing.
I imagine the UK Computer Misuse Act (eg at Section 3, http://www.legislation.gov.uk/ukpga/1990/18) probably covers it if the person who altered the TXT field does so to cause websites to load code on purpose, that purpose being for example to impair (Section 3(2)(a)) the running of the computer [causing Rick Astley to play, defo counts!] - but it can be read to cover pretty much anything.
Similarly I imagine something like the CFAA (18 USC 1030) probably has broad enough clauses to make this sort of action technically illegal, at least in some cases? But I'm out of my depth on that one.
Re: TXT Record XSS
#148Re: TXT Record XSS
#149Earlier quoted context omitted.
Ah, iodine. I've used it in airports, hotels, cafes - it's great. The only drawback is that it's slower than dialup and latency is off the charts. But when you're stuck on a cruise ship and internet access is $8 a minute, being able to ssh somewhere and browse the web and check your mail very slowly through links is worth it.
I usually just spoof mac addresses of people who already paid in most of those cases, the caveat usually being somebody had to pay.
I hope you're not still talking cruise ships here! Those folks are often paying high prices by the minute or by the megabyte for access: you'd be pretty literally stealing from your neighbors in that situation. (The moral issue for pay-by-the-day systems is one step further removed, but I think it's still real.)
Re: TXT Record XSS
#150I am half serious, but how about making HTML served in TXT records a standard trick for serving small web pages very quickly? There are way fewer network round trips: 1. DNS query for TXT record for example.com 2. DNS reply with HTML content Compared with the traditional 7 steps: 1. DNS query for A record for example.com 2. DNS reply with x.x.x.x 3. TCP SYN to port 80 4. TCP SYN/ACK 5. TCP ACK 6. HTTP GET 7. HTTP rep…
I wrote something like that but distributing torrents.
Wrote it AGES ago : http://netrogenic.com/dnstorrent/