HP3000-L Archives

June 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:
Dean Lavoie <[log in to unmask]>
Reply To:
Date:
Fri, 14 Jun 1996 06:30:00 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (54 lines)
Is the task of changing your systems support passwords so tedious or time
consuming that you avoid doing it, even though a key operator left swearing
profanity knocking over furniture and yelling that he would 'get even'?
If you can relate to this problem, then I have an offer for you.
 
Even though we use MPEX's Security package, there are still some 15 passwords
that remain on users and accounts (MANAGER.SYS, MGR.TELESUP, OPERATOR.SYS).
With 8 MPE systems that makes 120 passwords that need to changed. As a rule
I change them quarterly or when ever a key person leaves. There are also the
5-6 locations on each of our systems were we have embedded passwords such
as startup jobs when the system first comes up or DSCOPYI files that allow
a job to log on to other systems. I'm sure this is a task that all system
administrator's are familiar with and dread doing.
 
I developed a program I call PASSCHNG that generates all 120 passwords by
randomly selecting real words from a 50,000 word dictionary (I've edited the
dictionary it uses for words with 4-8 characters only). I simply reply
Y or N to accept or reject the words it picks. PASSCHNG then prints
the lists for all my designated distribution's (Operators, Sys Admin etc.)
other lists are sent via HPDESK automatically. This program then creates the job
PASSCJOB which when streamed sign's on to each of our systems, changes the
passwords and then edits the files which use embedded passwords. All I need to
do to complete the password changes is stream this one job. The time
involved for me now to change passwords is around an hour. Before PASSCHNG,
it was a least a full day job with all kinds of possibilities to incorrectly
enter a password or forget to change something. Best of all I don't have to
come up with all those passwords anymore.
 
For two years I have considered moving PASSCHNG into the CSL. The only problem
is that PASSCHNG requires two files as input that are unique for each site. The
first file is a script that contains the names of all your systems, the accounts
and users that need password changes and the distribution of each password. The
second script is a JCL which contains the actual commands needed to change the
passwords on your systems. Once these two script files are created minor changes
can be simple added in the future, such as adding new passwords to change,
adding files which use embedded passwords or adding users to the distribution
list. Total number of passwords to change and systems to maintain is unlimited.
 
PASSCHNG has been such a tremendous time saver that I still want to offer it
to everybody. I have decided to give PASSCHNG (both object and source) to
whoever wants it along with my services to create the customized scripts used
by PASSCHNG. I will simply charge a minimal fee for my services and shipping.
If you are interested or would like additional information please send your
request to [log in to unmask]
 
I will send you back a form to fill out with the information I need to
create the two customized files for your site. Once I receive the completed
form back I will create the two files and then send all needed pieces along
with complete instructions for use and maintenance on a DAT. Only upon
your satisfaction will I request compensation.
 
Dean LaVoie    Senior Systems Manager, - Walnut Creek, CA.
[log in to unmask]

ATOM RSS1 RSS2