🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.atari.st
Article #36556

Re: Right of reply, virus- public, private- a thin line

#36556
From: Greg Wageman
Date: Fri, 24 Feb 1989 16:47
56 lines
3397 bytes
In article <14940@cup.portal.com> Bob_BobR_Retelle@cup.portal.com writes:
>I agree that this is a sensitive matter...  the  *ONLY*  time I ever tried
>to surpress any Topic of discussion on GEnie was when the discussion of 
>"Trojan Horses" got too close to discussing  ACTUAL  methods of destructive
>programming..  (the term "virus" hadn't yet entered into things..)
> 
>I didn't want my Roundtable to be the inspiration for some 16-year old
>"hacker" to "make a name for himself" by using the information in a 
>destructive manner...  

Viruses and Trojan Horses came into being long before there were
computer conferences.  The solution to this problem is to educate
*everyone* about the nature of the beasts.  Keeping thousands of
innocent computer users ignorant to prevent giving the information to
a handful of jerks who can (and do) get the information elsewhere
(sometimes by discovering it themselves) makes little sense.

>Where do you draw the line...?   Are we better prepared if we see what most
>destructive programs look like..?  Or...  can we possibly avoid future
>problems by surpressing this information now..?

Suppressing the information???  What makes you think that you have any
control of this?  The information on how to write a virus is present
in any detailed system manual.  Any experienced programmed could write
a *killer* virus from the information in the Developer's docs.  It
doesn't always take a statement like "boot sectors make great places
to hide viruses" for someone who's mind works that way to see this.
The only information you are suppressing is that of how the current
crop of viruses work, and therefore the means to stop them.

>I'd like to see the source code for these "viruses", but who's to believe
>that *I* won't use them destructively...?

It isn't necessary to distribute working virus source code to
everyone; what is essential is that the method of operation of the
virus be thoroughly examined by experienced programmers, and the
information disseminated.  When the means of transmission and the hiding
places are known, it becomes simple to fight the disease.

Why not let "some 16-year old 'hacker' ... 'make a name for himself'"
by writing an *anti*-viral program?  Why do you assume that the
information *will* be used for harm?  You have a very cynical outlook
if that is the case.  Is it, perhaps that you are just protecting
yourself, and the rest of us be damned?


Longish .signature follows.  Skip now, or don't complain!

Greg Wageman			ARPA:  greg@sj.ate.slb.com
Schlumberger Technologies	BIX:   gwage
1601 Technology Drive		CIS:   74016,352
San Jose, CA 95110-1397		UUCP: ...!uunet!sjsca4!greg
(408) 437-5198
------------------
Opinions expressed herein are solely the responsibility of the author.
(And the author wouldn't have it any other way.)
Technical Details
Message-ID: <689@snjsn1.SJ.ATE.SLB.COM>
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!snjsn1!bilbo!greg
References: <415@odin.cs.hw.ac.uk> <14940@cup.portal.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!snjsn1!bilbo!greg
From: greg@bilbo (Greg Wageman)
Newsgroups: comp.sys.atari.st,comp.sys.apple,comp.sys.mac,comp.sys.ibm.pc
Subject: Re: Right of reply, virus- public, private- a thin line
Message-ID: <689@snjsn1.SJ.ATE.SLB.COM>
Date: 24 Feb 89 16:47:37 GMT
References: <415@odin.cs.hw.ac.uk> <14940@cup.portal.com>
Sender: news@SJ.ATE.SLB.COM
Reply-To: greg%sentry@spar.slb.com (Greg Wageman)
Followup-To: comp.sys.atari.st
Organization: Schlumberger ATE, San Jose, CA
Lines: 56