Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Re: Re: SelfChanging script!

by theAcolyte (Pilgrim)
on Aug 05, 2003 at 07:28 UTC ( [id://280908]=note: print w/replies, xml ) Need Help??


in reply to Re: SelfChanging script!
in thread SelfChanging script!

P.S. A note to all those who worry about these things - take another look. If some primitive self-replicating Perl source can cause any damage whatsoever, much, much worse will happen. Focusing on false threats at the cost of research is what's causing so many of our current problems. So I suggest you all get a clue, or at least stop spreading blind FUD. Thanks.
I'd like to ask first ... how is this indicitave of "much worse will happen"? There are plenty of cases of attacks on server where the basic methodolgy is to simply fill all available disk space on a partition. If this 'harmless' script gets executed with enough access, it could bring a server to its knees by filling it up.

If it was simply research, why the need to double itself in size? If its simply research, the problem is creating a persistant program that runs itself over and over. The way the question is posted smacks of either poor intents, or, even worse, a homework assignment.

Replies are listed 'Best First'.
Re: Re: Re: SelfChanging script!
by Anonymous Monk on Aug 05, 2003 at 08:18 UTC
    The way the question is posted smacks of either poor intents, or, even worse, a homework assignment.

    And you care if it's a homework assignment, why? Because someone is willingly allowing you to sabotage their education? Who cares, less competition for your job (which is a good thing for you if you think that Perl program is a major security threat). Or maybe because someone else will read the thread and learn in the process? Or that, when you're replying to the post, someone corrects an error of yours and you learn something new because of it? Gee, those homework questions sure do damage...

    If this 'harmless' script gets executed with enough access, it could bring a server to its knees by filling it up.

    If they have the privileges to execute this script and have malicious intents, they can do far, far worse than fill up some disk space. Worry about the privilege escalation first, then worry about more damaging options. After you've solved those, you can worry about filling up disk space.

    If it was simply research, why the need to double itself in size? If its simply research, the problem is creating a persistant program that runs itself over and over.

    Because that's the first thing that popped into his or her head? Because he wanted to learn more about the language and operating system he or she was using and decided this might be a good way? Maybe the goal was to test a new security tool.

    I'd like to ask first ... how is this indicitave of "much worse will happen"?

    Because far more damaging tools already exist. Because thousands and thousands of people know how to cause massive damage on a widespread scale. Unless people start getting a clue about these threats, we're going to problems that make every incident to date look like harmless pranks. By claiming that something like this poses a security threat, you trivialize the real threats and make people feel safe.

    Anyways, these problems aren't going to be solved on "Perl Monks" so I'll be on my merry way now. Later.

    A reply falls below the community's threshold of quality. You may see it by logging in.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://280908]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (3)
As of 2024-04-25 23:43 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found