HP3000-L Archives

August 2002, 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:
"Wayne R. Boyer" <[log in to unmask]>
Reply To:
Date:
Fri, 16 Aug 2002 00:26:31 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
In a message dated 8/15/02 4:05:30 PM Pacific Daylight Time,
[log in to unmask] writes:


> What's going on here is that, when $STDLIST is a spoolfile or a disk
> file, the CI scans the input line looking for something that resembles
> a lockword or password.  If it finds what it considers to be a lockword
> it removes it prior to echoing the line to $STDLIST.  The goal of this
> approach is to reduce the chances of revealing a file's lockword.
>
>

So if I write:

!COMMENT verify that the filename is correct and has a valid lockword
!COMMENT specified in the format: !FILE INDATA/LOCKWORD.DATA
!COMMENT
!FILE INDATA/MYSECRET.DATA
!RUN someprogram

I'm NOT going to see "LOCKWORD" or "MYSECRET" on the $STDLIST?
Same thing if I say:

!COMMENT check to see if the password for MANAGER.SYS is valid and
!COMMENT use this format: !JOB MANAGER/PASSWORD.SYS

No "PASSWORD" will show?

Experiments anyone?  I have dinner cooking and I'm hungry!
Wayne

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

ATOM RSS1 RSS2