iagox86

4 ms·

1.
by iagox86 11y ago
I could have, and perhaps next time, but I think <24h is enough information. :)
2.
by iagox86 11y ago
I edited the blog to make it more clear what happened - it was a typo I fixed. It didn't occur to me that it could be misconstrued, usually it's obvious that it's a typo fix, but in the case of the year it wasn't. :)
3.
by iagox86 11y ago
Yeah, it was a fixed typo, not a tongue-in-cheek comment. :) The vendor responded with a fix within hours!
4.
by iagox86 11y ago
This. Somebody pointed out my typo on Twitter. :)
5.
by iagox86 12y ago
Hey, I'm the guy who wrote this slide deck. You're absolutely right - as I replied to the parent, this talk has nothing to do with DNSSec, it wouldn't affect this one way or the other. I also didn't find any great tools
6.
by iagox86 12y ago
Hey, I'm the author of the talk, but I'm not the one who posted this. I'll give you some context :) It's the slides from a talk I gave yesterday at Derbycon - https://www.derbycon.com . It was recorded, but it
7.
by iagox86 12y ago
Hey, I'm the guy that wrote the talk and you're right - Iodone is similar in some ways. Some quick background - I wrote the original version of dnscat a few years ago, and AFAIK Iodine was made at the same time. dnscat was designe
8.
by iagox86 13y ago
Legal issues can get complicated. It's normal for a big company.
9.
by iagox86 13y ago
"There's a horrible vulnerability in the Bing app! ...but we're not going to give you any details." I hate stories like that.
10.
Ghost in the Shellcode: TI-1337 (Pwnable 100)(blog.skullsecurity.org)
4 points by iagox86 13y ago|0 comments