Ah.. point taken.. I was under the impression that you though it came in through some kernel hole.. But what the heck.. Regardless if the machine needs a reboot or not it's a year old.. you've had plenty of time to test/implement the patch ;)

February 27th, 2006, 09:36 PM

gore

That was pretty much my point as well. there was more than enough time to add the patch and it wouldn't need a reboot, maybe aweb server restart with apachectl stop then apachectl start

Hmm.. I was under the impression that Apache had a kind of 'soft restart' feature which allowed it to lose far less time online. I can't remember what it is called, but I'm sure it has something like that. :D

[edit] Sorry, I was thinking of the graceful restart - but apparently it doesn't do that, it only sets the restart for a certain point in time. Please ignore this post!

//me runs away and slaps himself

February 28th, 2006, 11:55 PM

slarty

I find it curious that the latest "Linux worms" attacks neither Linux nor any piece of Linux system software, but rather pieces of application software (Various PHP applications) which in fact might be equally vulnerable on Windows or anything else.

So the worms that we see attacking xmlrpc.php etc - the so-called "Linux" worms, are actually not Linux specific at all.

Mark

March 2nd, 2006, 08:08 AM

the_JinX

Quote:

Originally posted here by slarty I find it curious that the latest "Linux worms" attacks neither Linux nor any piece of Linux system software, but rather pieces of application software (Various PHP applications) which in fact might be equally vulnerable on Windows or anything else.

So the worms that we see attacking xmlrpc.php etc - the so-called "Linux" worms, are actually not Linux specific at all.

Mark

Not exactly..

They might just as well break into the Windows servers.. But the code they drop is linux specific..

And at that only x86 linux (or X86_64 with x86 compatibility)..

March 16th, 2006, 10:42 PM

Vorlin

Quote:

Originally posted here by J_K9 Hmm.. I was under the impression that Apache had a kind of 'soft restart' feature which allowed it to lose far less time online. I can't remember what it is called, but I'm sure it has something like that. :D

[edit] Sorry, I was thinking of the graceful restart - but apparently it doesn't do that, it only sets the restart for a certain point in time. Please ignore this post!

//me runs away and slaps himself

Code:

apachectl restart

That'll soft-restart apache sending the SIGHUP and not SIGTERM.

March 4th, 2008, 10:29 PM

tsunami

I would agree that the main reasons to scan for malware on a linux/unix box would be for mail scanning or scanning file stores (used by Windows users).
However, interestingly enough some *old* linux viruses are still doing the rounds.

On a slight side topic, the SophosLabs security blog is actually really interesting reading. Rather than them trying to sell you security software its a nice window into what a decent security firm is looking into on a day by day basis. http://www.sophos.com/security/blog/2008/03/

March 5th, 2008, 07:55 AM

SirDice

tsunami, you're replying to a thread that's almost 2 years old now..

But in light of that and having re-read parts of it. It's an urban myth you need root/admin access to get infected with malware. Hence no exploits are needed to turn your *nix box into a spambot. Just the casual user clicking on an executable. So there really is no reason why viruses like NetSky can't exist on *nix.

March 5th, 2008, 07:37 PM

tsunami

Quote:

Originally Posted by SirDice

tsunami, you're replying to a thread that's almost 2 years old now..

oops, i didnt look at how old the thread was. Oh well nevermind.

I agree completely, you can have malware cause untold issues on a machine without it ever having admin/root rights.

The biggest issue we see at the moment at work are linux boxes that get hacked and added into botnets rather than them being infected with malware. I put that down to linux/unix being used far more for servers. If it were used way more on the desktop then we would start seeing far more socially engineered attacks.

March 6th, 2008, 02:39 PM

The-Spec

Quote:

that on some OSs reboots are only for hardware and Kernel code and the maybe reason of why no one saw it at all.

Actually even in windows if you update a specific application alot of times it won't bother. And it's not as if you couldn't stop it from scheduling that through group policy.