I enumerated all IPv4 PTR records a few years back, and I saw a couple XSS things there as well. If anyone wants to host that data set somewhere, let me know, would be interesting to see what others do with it. Edit: I found my data and have a grep running on it, will share what turns up. Edit2: Somewhat less exciting than I remember: $ fgrep -- '>' * x.x.101.130.csv:1298607746,155.92.101.130, .nebula.msoe.edu. x.x.1…
How big is it? If you put up a torrent I'll seed it...
TXT Record XSS
91–100 of 236 posts
Re: TXT Record XSS
#92Earlier quoted context omitted.
Ah yes. The occasional click to confirm this or whitelist that, that's definitively "living hell". It's the users' resistance to the slightest inconvenience that makes security so hard.
It's really a hell. Average website over there is using at least 3 - 4 external domains for css, js, fonts and so. Getting a working website without nearly whitelisting many of them is highly improbable right now.
Whitelist places you trust. Keep things blocked that you don't like. If that breaks the experience, walk.
Re: TXT Record XSS
#93Earlier quoted context omitted.
https://archive.org please!
Do you know anyone there or anything about the process of getting something hosted there? I can burn the data to a DVD and snail mail it to them (or even drop it off in SF).
Only takes 5 minutes to create an account.
Re: TXT Record XSS
#94Re: TXT Record XSS
#95From any Linux (or probably OS X) workstation / server, you can run the command "host -t TXT jaimehankins.co.uk" ie: $ host -t TXT jamiehankins.co.uk ;; Truncated, retrying in TCP mode. jamiehankins.co.uk descriptive text " " jamiehankins.co.uk descriptive text "v=spf1 include:spf.mandrillapp.com ?all" jamiehankins.co.uk descriptive text " " jamiehankins.co.uk descriptive text "google-site-verification=nZUP4BagJAjQZO…
This is hilarious, but what's up with this line? >jamiehankins.co.uk descriptive text "v=spf1 include:spf.mandrillapp.com ?all" Why is mandrillapp.com (tranactional email startup) included?
Re: TXT Record XSS
#96"I acknowledge the code just written does not trust its input, under penalty of being whipped by a wet noodle."
But I guess folks would just click through.
Sigh.
Re: TXT Record XSS
#97Clever. I didn't get it at first. Never trust user input. Edit: See http://www.dnswatch.info/dns/dnslookup?la=en&host=jamiehanki... for the actual code.
Re: TXT Record XSS
#98Re: TXT Record XSS
#99Wasn't expecting that at all! Had several tabs opened and was really confused for a few seconds while I tried to find the tab with 'youtube on autoplay'. Firefox needs to show the 'play' icon for the audio tag.
For what it's worth, Chrome tells you which tab audio is playing from, it's nice.
Re: TXT Record XSS
#100I 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…
Why say that at all? Is it a way to fend off ridicule? Or does this show a lack of confidence in the idea and what you are saying?
Reminds me of comments that start "Am I the only one who thinks that..."
I've gotten out of the habit of apologizing for things that I say or prefacing them with phrases such as that. The reason is that I found that it was a lazy way to not give as much thought to what I was saying and whether I needed to vet my thoughts more.