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.
  • Holy crap! You mean it wasn't some script kiddie? Jeesh.

    As for legal action, it depends on how much you think you've been hurt. My initial inclination is to say yes, though it's too bad you can't go after the individual (or can you?). The company will probably settle anyway.

  • ...what you should do, but I don't think that you should let the threat of retaliation affect your decision.
  • Why where they DoSing you? For fun? Or "that'll teach them a lesson"?

    I say kill 'em all!

    • Re:DoS (Score:3, Insightful)

      We're an ISP. They were mailbombing a customer of ours (bouncing spam back to them through open relays). Apparently either a disgruntled ex-employee, or someone who got burned by them in one way or another. I don't have all the details sadly.

      Mostly I say "send out a message". I mean, what he was doing was illegal. But then again, I can't see the courts coming down too hard on him - the damages were a few hours work for a few people every time he launched an attack (which he did quite a few times). In all p
  • ... but I think yes, you should prosecute the individual. I really would hate to do it myself, but I really think threat of serious action is the only thing that stops them sometimes. So, someone needs to be the example for everyone else.
    • I have to agree. There are lots of script kiddies out there who think it's fun to waste time, money and resources by performing DoS attacks. As long as they feel they can act childishly without consequences, this behavior will continue.
  • Does that rhyme with "tosser"? I think the world ought to know.