HP3000-L Archives

September 1998, Week 4

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:
Larry Boyd <[log in to unmask]>
Reply To:
Date:
Wed, 23 Sep 1998 13:57:25 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
> Behalf Of Stigers, Greg ~ AND
> Well. I had my meeting with the data center admins, and there concern is
> that by not changing the LIMIT, even though we take down the server and
> listener jobs and NS itself, is that someone could dial into one of the
> old modems hanging off of a DTC. I love my job. I am very hard pressed
> to imagine this actually happening. This is not a normal means of access
> for anyone besides HP and a few vendors. Should I be concerned? Are
> there other solutions for preventing such access besides dropping the
> limit?
>
> After pursuing some other solutions, and having someone disavow all
> knowledge of the CSL tape, I am going to propose that we $ALLOW LIMIT
> SHUTDOWN,OPERATOR.SYS STARTUP,OPERATOR.SYS in SECURCON.DATA.VESOFT.
> Thanks to VeSoft for suggesting this, when I called their support about
> a related problem with how the original operator command file uses MPEX
> ABORTJOB (when put into a job, the job killed itself...). And thanks to
> the various respondents to this post and the previous post on clean
> running backups.

You could DOWN the modem ports.  This will not allow anyone to log on
through those ports.

lb

ATOM RSS1 RSS2