[1270] in Public-Access_Computer_Systems_Forum
Are all public-access resources public?
daemon@ATHENA.MIT.EDU (Public-Access Computer Systems For)
Tue Sep 22 11:33:41 1992
Date: Tue, 22 Sep 1992 10:27:08 CDT
Reply-To: Public-Access Computer Systems Forum <PACS-L%UHUPVM1.BITNET@mitvma.mit.edu>
From: Public-Access Computer Systems Forum <LIBPACS%UHUPVM1.BITNET@mitvma.mit.edu>
To: Multiple recipients of list PACS-L <PACS-L%UHUPVM1.BITNET@mitvma.mit.edu>
2 Messages, 73 Lines
*-----
From: Genny Engel <gen@magnum.ucop.edu>
Subject: Re: Are all public-access resources public?
> THE ISSUES I WAS HOPING TO DISCUSS ON PACS-L ARE THESE:
>
> A. Should the Internet community feel obliged to ask
> permission of the host before sharing information about
> new resources?
Yes, I think we should, if we have the slightest question about them. If a
new library catalog system shows up in a well-known guide it is reasonable to
assume that information about the system can be passed on. But if you try out
the system and find out it has unpassworded access to a licensed database, I
think it is at least our responsibility to double check with that system's
administrators on whether it is OK to publicize their catalog. If they know
it includes licensed resources and this is not a problem, then they are the
ones who would know it is not a problem.
I would draw a big distinction here between access to databases and access to
other systems, however. If you test out someone's system and find out it
allows some egregious security error like anonymous access to full-service
telnet, PULL THE PLUG. Do not publicize this system! You are being at least
as irresponsible as this wayward host if you publicize the host.
> C. Given the nature of the Internet, it is nearly impossible
> to stop the flow of information that people find valuable.
Yes, this is basically because everyone feels that given the nature of the
Internet, it is nearly impossible to stop the flow of information that people
find valuable! In other words, I might as well publicize this since someone
else will anyway. But if we are all considerate enough not to publicize
sources that don't wish to be publicized, in the long run people will turn to
the sources that do wish to be public, and our users will not experience the
sudden yanking away of services that is bound to occur when the people running
a particular service feel it is being abused.
I'm not sure you're aware that service providers can and do pull the plug on
public access when their public gets too big. If you feel you have a valid
reason to get a special access OK from a given provider, ask that provider if
it's OK! If you get a "no" it may very well be that your users won't be well
served by this source anyhow, since it only has 3 ports.
Genny Engel
MELVYL System User Services
University of California
gen@magnum.ucop.edu
*-----
From: SOLIBMD@GSVMS2.CC.GASOU.EDU
Subject: Public access to databases debate
I was intrigued by Mr. Caswell's comments about being open, etc. in
academia. I certainly do agree that academic institutions are not in
the business of denying access to materials, but we really don't want to
be the "test case" of a database producer who might wish to set an
example of one who did not abide by password and access restrictions for
particular products. That is why we agonize over how to control access
to specific databases so that we cannot ever be questioned about being
within the letter of the law pertaining to our contractual agreement
with a database producer. Yes, we certainly would like to provide access
to anyone who might need it, but we are bound to our contractual
agreements and we work closely with our computer center staff to insure
that materials are accessed according to our promises. We are thankful
to have a good working relationship with our computer center such that
we can discuss and implement security restrictions as necessary, both
for the protection of our contracts and of our own campus computing
facility.
Mary K. Dudman
Systems Librarian
Georgia Southern University
INTERNET: solibmd@gsvms2.cc.gasou.edu
