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

    • It's hard to be sure whether other slides are meant to support the sux statement or define it, so I just quoted the sux statement and some other slide without assuming anything.

      Why in the world would you quote something you clearly don't understand?

      "I saw it on the internet so it must be true!!"

        - ask
      --

      -- ask bjoern hansen [askbjoernhansen.com], !try; do();

      • Because it was written by a notable author and I was quoting it, not interpreting it in a way I was unsure of. It was written as though "sux" was the bottom line, and it would have been ok to quote it even if I quoted nothing else. I provided a link to the source. Other Wikipedians could have given the module the benefit of the doubt and added more details if they thought it would clarify things. Quoting "sux" was appropriate whether there's total suckiness or not, if that's what a notable author and edito