I do the same as Chris,

Random passwords are assigned on a daily basis.  Since we have 'SLEEPER'
invoke MPEX we use its 'randomname()' function (see below):

Regards
Paul Christidis
...
altacct snads   ;pass=![randomname()]
altacct softrep ;pass=![randomname()]
altacct support ;pass=![randomname()]
altacct syslog  ;pass=![randomname()]
altacct sysmgr  ;pass=![randomname()]
altacct techxl  ;pass=![randomname()]
altacct telamon ;pass=![randomname()]
altacct timewarp;pass=![randomname()]
altacct tym     ;pass=![randomname()]
altacct vecsl   ;pass=![randomname()]
altacct vesoft  ;pass=![randomname()]
altacct www     ;pass=![randomname()]


HP-3000 Systems Discussion <[log in to unmask]> wrote on 01/18/2005
12:43:26 PM:

> donna garverick <mailto:[log in to unmask]> wrote:
> > --- "Newton, Ernie" <[log in to unmask]> wrote:
> >
> >> Greetings,
>
> >> Vladimir visited us last week and again raked me
> >> over the coals for inadequate securities.  It's an
> >> annual occurrence.
> >
> > just say no :-)
> >
> >> That being said, there are things I need to do.  I found
> >> some logons without passwords and am curious about any
> >> ramifications there may be if I put an account password
> >> there.  These seem to be "system" accounts that include;
> >> APACHE, JAVA, HPPL89, etc.
>
> I run jobs every 24 hours on all my systems that put random account,
user,
> and group passwords on all these "system" accounts; in fact ANY
> account/user/group that isn't used on a regular basis by real users.
(using
> contributed rndpass program on www.3k.com )
>
> Just make sure that any startup jobs/ sysstart etc utilize the
:JOBSECURITY
> settings, or you use a utility that negates the need for imbedded
passwords
> in job streams.
>
>  -Chris Bartram
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *