SirCam on Linux via WINE

illusion_2K writes "Another monumental step forward for Linux - the SirCam virus now works on Linux via WINE. ("With a few ommissions")" Allright I had to post it. Thats damn funny. We can emulate worms if we want to!

Comments

The major barrier to virii...

[gusnz]

Now, all we need is an Outlook user simulator package that automatically opens executable attachments if it's asked for advice :)

Not Quite

[Jerry]

While I noticed that SirCam infected email did fire my Wine program the results were a dud. The effect was that SirCam was exposed but not functional, and I was able to explore it's code without fear. There were no registries to infect, no exchange list to exploit, and the "hidden" trojans were easily seen and removed.

SirCam it totally harmless on Linux under Wine.

Great

[LazyDawg]

Now even Linux users can enjoy the benefits of the Microsoft Virus Infection Layer in their otherwise high quality operating system.

This is a big step for Linux's acceptance as a Desktop operating system. We NEED more clueless newbies out there using Linux and saying "fuckit, I think there's a virus on your/my system. Time to reinstall KDE."

In a few months even Outlook will be available to Linux/Wine users, so too will be the full Universal Virus Infection suite of tools from Microsoft.

My only question is, how much longer until we have kernel-level support for VBA and Microsoft Scripting?

Makes perfect sense to me...

[Ungrounded Lightning]

My original point (which has been moderated into oblivion, as I assume this will be too) is that it doesn't make ANY rational sense to be trying to get a MALICIOUS program running on your system.

It makes perfect sense to me, with a couple of changes of emphasis.

It makes sense, when writing an emulator/compatability layer, to TEST whether a malicious program will run, for two reasons:

Discovering whether the emulation is close enough that the emulator is also vulnerable to the malicious software.

Discovering whether the malicious software fails because it depends on a feature - necessary for some NON-malicious programs - which is not correctly emulated. (A malicious program may use a little-known or undocumented "feature" - perhaps one that's been keeping some popular apps from working correctly.)

But beyond debugging the emulation there are additional reasons:

Running the malicious program in the (open-source) emulation environment may provide additional insight into its operation, leading to better defenses, both for the emulation and the original environment.

It's FUNNY!

That's four separate reasons that this makes sense.