Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • So, I guess you think it's wacky for me to be against a publisher who post-copyrights technical books, which people tend to want to be up-to-date, and a publisher of a book that "Rather than simply describing the vulnerabilities and their exploits theoretically or showing you how to use pre-existing tools to exploit the vulnerabilities...provides the nuts & bolts you need to learn how to program your own exploit code." At least you linked to my post, but I'm wondering exactly what you disagree with abou

    • Mmmm, I missed that:

      “Rather than simply describing the vulnerabilities and their exploits theoretically or showing you how to use pre-existing tools to exploit the vulnerabilities…provides the nuts & bolts you need to learn how to program your own exploit code.”

      I have explained to a number of people how to conduct SQL injection attacks. Will you boycott me now?

      • It's not as bad if you're selective about who your teaching, and it depends on why you're teaching them, but yes, I'll boycott you too. Not sure what you sell though.
        • I would also like to be boycotted. I have written an article, in The Perl Journal or maybe The Perl Review, one of the two, about how to do SQL injection attacks AND hack poorly written CGI scripts, on the way to explaining why taint checking is a good thing. What do I need to do to be boycotted? Is my bringing it to your attention here sufficient? Is there some form I need to fill out? Please reply at your earliest convenience.
          --

          --
          xoa