HP3000-L Archives

April 1995, 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:
"Paul H. Christidis" <[log in to unmask]>
Reply To:
Date:
Thu, 13 Apr 1995 10:26:12 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Wayne!
 
How about trying one to the following:
 
1.  Since the program uses PRIV mode, how about gaining SM capability
temporarily and using the FINFO("fname",33) to get the lockword and then
open the file for reading. (You need to find how to gain SM capability).
 
2.  Again in PRIV mode you could call the DIRECFIND procedure using the
file name (I assume that you are using it to get the user and account
passwords).  Some place in the returned buffer there is the label address
that could then be used to get the lock word.
 
3.  Have the program used by the operators, simply write the file name of
the stream file to a message file that is being monitored by a background
process under a batch user with SM capability.  That process then can
perform the lockword and password determinations and stream the job.
 
Just some thoughts.  Good luck.
 
Regards
 
Paul H. Christidis
[log in to unmask]      (714) 732-7114
 
 
 
 
______________________________ Reply Separator _________________________________
Subject: Help with security problem
Author:  [log in to unmask] at CCGATE
Date:    4/6/1995 4:40 PM
 
 
I have a program I'm converting from an old MPE/V system to a new
957 system.  This program assists operators with streaming
programs for batch production.  It calls the MUSTOPEN intrinsic
with an aoptions of %17 while in priviledged mode.  This would let
the program bypass a file's lockword and security access and and
grant read access.  From there I make a local copy of the file,
insert the current passwords for the user and account and then stream
the local copy.  However, I've found that MUSTOPEN no longer works
that way. If necessary, I can force the users to release and put
lockwords on their files, but this will lead to other problems, like
users that do not properly release and lockword their files after they
change them.  Any ideas or hints would be welcomed.
 
            ...........Wayne

ATOM RSS1 RSS2