Beefy Boxes and Bandwidth Generously Provided by pair Networks
Come for the quick hacks, stay for the epiphanies.
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
White hat hackers recruit from black hat ones, at least sometimes.

Answering a question here is not answering just the OP. Anyone having similar questions, or just browsing the forum, might be interested in the answers.

If the post itself doesn't contain any malicious code, #3 is definitely the correct way to go. By "educate", though, I don't mean giving them what they want; you can include all your ethical concerns into the reply, which might not interest the OP, but can help other script kiddies to consider changing their paths, and maybe change their hat from black to grey at least. You can always answer correctly but in a way that the answer can't be used without real understanding, i.e. show the solution to a slightly different situation that can still help some else who finds the page, but not the phishing scammer who just requires copy-n-paste ready source code.

Sometimes, repeating the same answer again and again (even to different people) leads to exhaustion. If that's your case, use #1.

I'd reserve #2 for posts directly containing or linking to malicious code.

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

In reply to Re: Ethical considerations of responding to posts made by someone obviously up to no good by choroba
in thread Ethical considerations of responding to posts made by someone obviously up to no good by kikuchiyo

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (5)
As of 2024-03-28 14:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found