Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!rice!uw-beaver!milton!fetrow From: fetrow@milton.acs.washington.edu (David Fetrow) Newsgroups: alt.flame Subject: Re: Computer Abuse / Product Liability / Criminal Statutes / ECPA Message-ID: <1483@milton.acs.washington.edu> Date: 20 Jan 90 02:52:02 GMT References: <22359@usc.edu> <4948@sugar.hackercorp.com> <9738@hoptoad.uucp> <5527@udccvax1.acs.udel.EDU> <672@cs.nps.navy.mil> Reply-To: fetrow@milton.acs.washington.edu (David Fetrow) Distribution: na Organization: University of Washington, Seattle Lines: 26 >In article <672@cs.nps.navy.mil> jxxl@cs.nps.navy.mil (John Locke) writes: > >Am I the only sysadm who thought the entertainment from this "worm" more >than compensated for any time lost or inconvenience? No and that annoys some of us a lot. There are applications where a couple days lost is more than inconvenient but the workstations in the operating rooms are on a seperate net and weren't being used yet anyway (application is displaying 3-d medical scans). As a system administrator I wasn't all that upset for myself (after it became apparent the worm was benign except as a resource hog...until then it was maalox city) but that worm messed with my users. I can appreciate the clever bits of the code, that there were elements of an accident here (some percentage of the mess was accidental I'm sure) and who of us hasn't messed up but dang: This guy messed with my users and that's hard to stay totally calm about. -- -dave fetrow- fetrow@bones.biostat.washington.edu dfetrow@uwalocke (bitnet) {uunet}!uw-beaver!uw-entropy!fetrow "CP/M: Remember when fast, small, useful and clean were good?"