[WEB4LIB] Locking down public access terminals

[Avi Janssen]

I am also setting up an OPAC running Win95 on an NT network.  Has anyone
come across a detailed checklist of how to lockdown such a setup?  I also
implemented a system policy to remove many commands in Win95, but I'm sure
I'm forgetting something.  (Office95, IE4.0 and Netscape are also
installed.)
Seems like there should be an FAQ or something similar somewhere.  If such a
checklist doesn't already exist, I'd be willing to compile the responses.
Thanks.

Avi Janssen (avi at spertus.edu)
Information Services Manager
Spertus Institute of Jewish Studies
618 S. Michigan Ave.
Chicago, IL  60605
voice: 312-322-1736
fax: 312-922-6406


> -----Original Message-----
> From: web4lib at webjunction.org
> [mailto:web4lib at webjunction.org]On Behalf Of Peter Schlumpf
> Sent: Tuesday, September 14, 1999 7:07 PM
> To: Multiple recipients of list
> Subject: [WEB4LIB] Locking down public access terminals
>
>
> I have the job of developing and deploying public access Internet
> terminals.  These will be running Windows 95 and Netscape Navigator
> standalone (version 4.08).  By running Netscape in superkiosk mode (-sk)
> and with a little Javascript I've been able to make these things
> relatively tamper proof -- all the user sees is a browser screen with
> just the basic navigation buttons, no access to browser settings, the
> taskbar, etc.  What I still need to address is  to surpress dangerous
> key combinations: CTRL_ALT_DEL, etc. and to eliminate the ability to
> download files from the network using the browser.  I'd be very
> interested in hearing about any software, hardware or methods that
> anyone has employed to deal with these two problems (or any other
> related security issues). I'm sure a lot of people have had to deal with
> these problems before.
>
> Thanks in advance!
>
> Peter Schlumpf
> North Suburban Library System
>
>