[NIFL-TECHNOLOGY:116] Re: Techno Tyranny

From: Steve Linberg (stevel@literacy.upenn.edu)
Date: Mon Dec 15 1997 - 12:20:08 EST


Return-Path: <nifl-technology@literacy.nifl.gov>
Received: from literacy (localhost.nifl.gov [127.0.0.1]) by literacy.nifl.gov (8.8.7/8.8.5) with SMTP id MAA27294; Mon, 15 Dec 1997 12:20:08 -0500 (EST)
Date: Mon, 15 Dec 1997 12:20:08 -0500 (EST)
Message-Id: <l03130300b0bb12b89159@[130.91.108.80]>
Errors-To: lmann@literacy.nifl.gov
Reply-To: nifl-technology@literacy.nifl.gov
Originator: nifl-technology@literacy.nifl.gov
Sender: nifl-technology@literacy.nifl.gov
Precedence: bulk
From: stevel@literacy.upenn.edu (Steve Linberg)
To: Multiple recipients of list <nifl-technology@literacy.nifl.gov>
Subject: [NIFL-TECHNOLOGY:116] Re: Techno Tyranny
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Status: RO

David Rosen spake thusly:

>A teacher told me that they have a new network of terrific pentiums at
>her program which apparently is connected to a Wide Area Network.  Her
>program is one of several adult literacy programs sponsored by a city
>agency. The WAN/LAN administrator(s) have a policy that no software
>may be installed or used on any of the computers unless it is first
>approved by a central committee downtown.

I think this is unfortunate, to say the least.  I can understand the
concern: viruses can be spread by careless use of casually-installed
programs and compromise the security and stability of the network.

There are two components to a solution to this problem: (a) prevention and
(b) preparedness for rebuilding if the network goes down.  A good solution
involves both of these components to a degree.  What it seems that these
network administrators have done, since (a) is easier than (b), is make a
hard-and-fast rule about computer use, in the hopes of never having to do
(b).  I wish I could say this was rare.

I personally disagree with this philosophy for two reasons: (a) it stifles
spontaneous use of the computers by people who already know what they're
doing (and I believe spontaneous creativity is the source of genius and
often the best use of the computer tool), and (b) it's unrealistic.  Sooner
or later your network *is* going to go down and you have to be ready to
deal with it.  It's not even that hard, if you're prepared, so viewing it
as an apocalpytic situation to be prevented with apocalyptic precautions is
unfortunate.

I think a better solution, albeit one that takes more work on the part of
administrators, is this:

First, a triple-redundancy backup system that kicks in at 2:00am daily to
back up the entire system to tape, in the event of a complete loss, must be
put into place if it doesn't already exist.

Second, administrators must be able and ready to restore from tape with
very little notice.

Third, every computer on the network should be equipped with virus-scanning
software, and all users should be educated about viruses and probably sign
an agreement stating that they will always scan for viruses before
installing or using software, and assume responsibility for dealing with
whatever the consequences are on *their* machines.  Those that don't feel
comfortable doing this can sumbit their software to the central committee
(or whoever) for proper review.

Another concern that may be leading to this clampdown is that of unlicensed
software, which would create legal problems for the entire network.  It
needs to be an absolute rule that *all* software used on the computers be
properly licensed - and this includes shareware.  Those of us who "borrow"
our colleagues' Microsoft Office CD to stay up-to-date are violating
licensing agreements that can land the supervising authorities in very hot
water if a software audit takes place.  Some administrators, in fact,
conduct unannounced software audits in their areas of jurisdiction for
precisely this reason.  This is entirely legitimate, and users need to be
educated about the importance of licensing issues.

In general, I believe that education and individual responsibility are a
far better choice than arbitrary and stifling restrictions, but it does
take more work.


*********************************************************************
Steve Linberg
Systems Programmer and Technology Specialist   (general) 215-898-2100
National Center on Adult Literacy             (tech lab) 215 898-0668
Graduate School of Education                       (fax) 215-898-9804
University of Pennsylvania
3910 Chestnut Street           e-general: slinberg@literacy.upenn.edu
Philadelpia, PA  19104        e-listserv:   stevel@literacy.upenn.edu
*********************************************************************



This archive was generated by hypermail 2b29 : Tue Jan 11 2000 - 13:27:05 EST