> -----Original Message-----
> From: Donna Garverick [mailto:[log in to unmask]]
> Matt Pereira wrote:
>
> > My coworker's line of thinking was that the
> > embedded passwords didn't need to be removed from the
> nightly jobstream
> > since they're not looked at anyways due to JOBSECURITY now
> set to LOW, and
> > PASSEXEMPT set to MAX. Am I being overly paranoid or
> rightly concerned?
>
> my guess is the 'password' algorithm sees that the password
> is literally in the
> job stream and quits trying to figure it out...but it's hard
> to say.  jeff vance
> is right when he said you really really really don't want
> passwords embedded
> into your job streams (with paraphrasing provided by donna
> :-)          - d

Actually, there is a "rationalized" reason for keeping embedded passwords,
however, to properly "rationalize" the reason, you need to CHANGE all the
actual active passwords.  Basically, by leaving KNOWN BAD passwords in the
file, anyone "snooping" the files will not get the "real" password.  Of
course, there is a downside to this, but it isn't (much) different than
taking them out: in the event the external password-replacing software
fails, you need to supply the PROPER passwords at submission time, and if
there are "wrong" passwords already in the file, you might NOT be prompted
for the "correct" password...