| Hi,
>> non-prived user CANNOT even do directory of this directory
Have you checked the prots on all the parent directories, back up to
(and including) 000000.DIR? Is the device itself protected against world
access? (Not sure if you can do that on VMS, but it's an idea)
Note that W:E on a directory will allow someone to access something in the
directory by name, so I could do (eg) $dir [a.b]c.txt but not $dir [a.b]*.txt
W:R on a directory allows someone to do wildcard operations on the directory
(ie it lets them actually 'read' the directory to find filenames).
Scott
|
|
Hi,
First some remarks:
> I'm hoping that someone here mihgt be able to shed some new light. The
> customer has a script (in CM) in oa$site_do_share. The script has w:RE
> and is owned by ALL-IN-1.
The BLP, DO and SCP directories should now be closed for the world (V3.0,
V3.0-1):
Directory DKB200:[ALLIN1V30_DEV.SITE]
DO_SHARE.DIR;1 OA$MANAPP (RWE,RWE,RE,)
(IDENTIFIER=OA$MANAPP,ACCESS=READ+WRITE+EXECUTE+DELETE)
(IDENTIFIER=OA$MANAPP,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE)
(IDENTIFIER=OA$PRVAPP,ACCESS=READ)
(IDENTIFIER=OA$PRVAPP,OPTIONS=DEFAULT,ACCESS=READ)
(DEFAULT_PROTECTION,SYSTEM:RWED,OWNER:RWED,GROUP:RE,WORLD:)
As all files of this directory end up in the TXL the files cannot be called from
the directories directly any longer.
So, that's the theory.
> -< Did you TXL the script ?? (SM CSZ CCM) >-
>-------------------------------------------------------------------------------
>
> %OA-E-SCPOPEN, Error opening SCRIPT file "OA$DO:3M_PORT"
> -RMS-E-PRV, insufficient privilege or file protection violation
>
> re .1 - yes TXL was redne, ALL-IN-1 exited and reentered.
The procedure is called directly via OA$DO:, so the TXL isn't used.
Try the following:
Modify the protection of [.SITE]DO_ENGLISH.DIR for W:RE. The reason is you use
OA$DO: as directory specification. The first directory in this search list is
OA$SITE_DO_LLV (ENGLISH), which you cannot access. So ALL-IN-1 bumps out.
HTH,
Simon
|
| Or, if for some reason * they want to refer to the file itself rather
than the TXL version of it, then it shouldn't be in OA$DO (move it to
OA$LIB: perhaps).
* for example, supposing they had found some script code combination
which didn't work in TXLs - no, silly me, ridiculous.
D.
|
| well,
thanks to all - the problem is solved! i modified the prot according
to .5 and things are ok.
re .7 - i'd love to get rid of/or at least modify the location of the
script, but its in too many print destinations. beleive me, at this
customer you don't want to change anything!
ann
|