From owner-freebsd-security Wed May 20 12:22:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04457 for freebsd-security-outgoing; Wed, 20 May 1998 12:22:10 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from bofh.shmooze.net (markjr@bofh.shmOOze.net [205.210.42.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04331 for ; Wed, 20 May 1998 12:21:46 -0700 (PDT) (envelope-from markjr@bofh.shmooze.net) Received: (from markjr@localhost) by bofh.shmooze.net (8.8.5/8.8.3) id PAA06101; Wed, 20 May 1998 15:21:35 -0400 Message-ID: X-Mailer: XFMail 1.3-beta-042198 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3562A6DB.3412BC8B@elr346.ateng.az.honeywell.com> Date: Wed, 20 May 1998 15:21:35 -0400 (EDT) Reply-To: Stunt Pope Organization: Private World Communications From: Stunt Pope To: Emmanuel Gravel Subject: RE: Virus on FreeBSD Cc: freebsd-security@FreeBSD.ORG Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk On 20-May-98 Emmanuel Gravel wrote: > I haven't heard of a virus made for a Unix-like OS before, but I'm > wondering if this can be an issue with FreeBSD (or Linux for that > matter). I'm saying this since they both run on the most common > platform there is today, the PC. I know most virii were writen for > DOS-like OS's, but it's my impression that the common point between > both machines is the hardware. > > Can anyone either clear this for me, or point me in the right direction > for some info? > Checkout the Bugtraq archives, and search on "linux virus", there was one released last summer or so, mainly as an exercise IIRC. Can't remember the name of it though. (http://www.geek-girl.com/bugtraq/) -mark --- Mark Jeftovic aka: mark jeff or vic, stunt pope. markjr@shmOOze.net http://www.shmOOze.net/~markjr Private World's BOFH http://www.PrivateWorld.com irc: L-bOMb Keep `em Guessing To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message