merlyn you sure get combative when challenged on your assumptions. You don't know why he wrote the script. Your conclusion is based on an assumption

You could have avoided this whole mess by using a little tact and offered some wisdom. But with typical chest beating you basically declared him to be a wannabe hacker and or a script kiddy.

It's rather funny as I seem to recall you getting incensed that people keep stating to you that you think that code should not be posted here unless it is written by someone of your level. Then I read in another thread:

The message that triggered this thread was not written by either an expert in security or an expert in Perl. It's a Perl beginner program, whose purpose initially appeared to be to be nothing more than a junior cracking tool.

This place is supposed to be about learning. A port scanner can be abused as many other things. Everything does not require a disclaimer. We don't see them on Guns and shoot for that matter I guess we could put a disclaimer on pens as they technically could be used as a weapon.

And what is this?

Furthermore, and more importantly, we cannot have the Monastery seem like it harbors people who experiment with cracking tools. We must take a stand, or it will undermine what I believe to be the purpose of the Monastery. Now, if vroom counter-argues, I'll be happy to listen. But that would be a pretty decent shock, given that the Monastery is now also an element of YAS/TPF, which inherited the PerlMonks mission, which also inherited the Perl Institute's mission, of which I was a founding board member (and significant contributor) of both. Stonehenge has also been a significant contributor to YAS/TPF. If vroom chooses to harbor crackers, then I will ask the YAS/TPF board to disown the Monastery. You can't have it both ways.

You going to hold your breath until you get your way?

Rather then assuming, you might ask some questions. This place does not harbor crackers. Awhile back a person posted a rather lame virus script Problem with quotes. People challenged him and he tried to hide his mistake by changing the original post.

Just admit it. Your intent was right but your approach could have been better

In reply to Re: •Re: Re: •Re: Re: •Re: pscanner.pl by Marza
in thread pscanner.pl by /dev/null

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.