Re: Restricting terminals

[Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>]

Devices... TCP/IP or Twinax?

TwinAx:
What I did was allowed auto config, then went and renamed the
devices to something that was meaningful to me when I had the spare
moment.  It created W1 W2 W3 W4 etc...  I went back and renamed them
D_VIVIAN
D_BRIAN
D_JOSE
or whatever.  Since these are tied to a port/switch combination, the
physical tube was what was set up.  If someone was very knowledgable and
were on the same port, I guess they could change the switch setting on
their dumb tupe and wait for the other user to log off then turn their
tube on to grab the display name, but then you could always set a password
in the tube configuration.

TCP/IP:
I have a number of Client Access installs that use a blank device name, so
that they create a device QPADE00001 or whatever.  The majority of the 
sessions, however, are named LTL753 LTL751 CNX223 or whatever we choose.
Now we limit the devices to them by the configuration.

This is a little less secure than the twinax method, I think, because I can't
think of anythign to keep a knowledgable user from changing their session name
and reconnecting when the other person isn't logged in.

Regards,

Jim Langston

Date: Wed, 9 May 2001 14:32:33 -0500
Subject: Re: Restricting terminals

We use the auto configure for display devices that allows display device
descriptions to be defined as needed and acquired. We have need for a
couple of devices to be restricted to a few users. We can figure out how to
make sure those select few get those dedicated terminals, but how do we
keep others from jumping in and getting those dedicated terminals?


Dave Snyder
Systems Analyst
Sterling Financial
Phone: 717-735-5876
dsnyder@sterlingfi.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---