HP3000-L Archives

October 1996, Week 2

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:
Stuart Smith <[log in to unmask]>
Reply To:
Stuart Smith <[log in to unmask]>
Date:
Tue, 8 Oct 1996 10:39:01 PDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
     NBSpool will strip embedded passwords and lockwords from the display.
     I have not tested with passwords that have been added by STREAMX or
     NSD.

     Stuart Smith
     Quest Software


______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Reading Input Spoolfiles
Author:  Tracy Johnson <[log in to unmask]> at Internet-Link
Date:    10/8/96 10:32 AM


I just tested reading an #I file using MPEXs PRINTI command.  I did not
find the password displayed.  We do have STREAMX enabled.  There is a
comment area added that says what the stream file name is, who streamed
it, on what LDEV, and a date time stamp, but no passwords.  If there was
a lockword embedded, perhaps it would be displayed.
 ----------
From:  owner-hp3000-l[SMTP:[log in to unmask]]
Sent:  Tuesday, October 08, 1996 9:15 AM
To:  HP3000-L
Subject:  Re[2]: Reading Input Spoolfiles

One caveat, here, is that input spoolfiles might contain passwords or
other data substituted at stream time (STREAMX and JMS/3000 can do
this) which you don't want exposed.  NBSpool and ESPUL (we use both for
various reasons) have the capability of securing input spoolfiles.  I
consider ESPUL more robust in this regard, being able to secure this
for individual users or groups of users, where NBSpool accomplishes
this by setting a password for INPUT mode.

Lee Gunter          [log in to unmask]
HMO Oregon

ATOM RSS1 RSS2