HP3000-L Archives

May 1996, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mike Farrell <[log in to unmask]>
Reply To:
Mike Farrell <[log in to unmask]>
Date:
Fri, 17 May 1996 17:16:06 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
It has come to my attention recently that if I want to connect my LAN to
my HP3000 via a network connection (which thanks to many of you I now
know how to do) that I am, in one sense, opening myself up to a whole new
slew of security breach possibilities. Your comments on the following are
welcomed:
 
It has recently dawned on me that accessing the HP3000 via a network
connection is a very different process than accessing the HP3000 via a
DTC connection and that my system may become MORE vulnerable than
previously imagined. I have heard that traditional type security
solutions which use logon UDC based processes may open up a "loop hole"
when used in a networked environment. Is this true? Apparently the most
serious problem as I meagerly comprehend it is that logon-UDC
authentication of a user occurs AFTER rather than BEFORE logon.
 
While our system is not yet networked to the 3000 I would appreciate any
comments about this "propaganda?" and what can be done if in fact this is
an additional security threat.
 
As always I am humbly yours,
 
 
--
Mike Farrell
Intermountain Gas Company
Data Center Operations Supervisor
555 South Cole Road
Boise,  ID  83707

ATOM RSS1 RSS2