From owner-freebsd-chat Wed Mar 28 4:53:58 2001 Delivered-To: freebsd-chat@freebsd.org Received: from fl_exchange.fl.dk (gw.fl.dk [193.88.152.147]) by hub.freebsd.org (Postfix) with ESMTP id 7C42E37B71E for ; Wed, 28 Mar 2001 04:53:55 -0800 (PST) (envelope-from bostergaard@siticom.com) Received: by fl_exchange.fl.dk with Internet Mail Service (5.0.1460.8) id ; Wed, 28 Mar 2001 14:50:33 +0200 Message-ID: From: =?iso-8859-1?Q?Bryan_=D8sterg=E5rd?= To: 'Terry Lambert' Cc: chat@FreeBSD.ORG, rsidd@physics.iisc.ernet.in Subject: RE: Virus targetting both Windows and Linux? Date: Wed, 28 Mar 2001 14:51:00 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Is this at all possible? >> http://dailynews.yahoo.com/h/nm/20010327/wr/virus_winux_dc_1.html > >Maybe if you had WABI or WINE installed. > >It would be hard for a virus to be executable on more than one >platform at a time, unless it wasn't really a virus. The way this virus works, is as follows: It has one Linux ELF image capable of infecting both Linux ELF and = Windows PE files. It has one Windows PE image capable of infecting both Linux ELF and = Windows PE files. This doesn't mean the same file will be able to run under both Windows = and Linux, quite the contrary. So it's simple a Linux program capable of editing (infection) to = different executable formats, as well as a Windows program capable of the same. I hope this explanation clears up any confusion as to the possibility = of such a virus. As for spreading, Benny (the author of Winux) thinks that it should be = able to spread from Linux to Windows, as many users have a FAT (Windows) partition mounted, for exchanging data. As far as I know he haven't explained how the Windows version of Winux would spread to Linux. Bryan =D8stergaard bostergaard@siticom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message