HP3000-L Archives

March 1999, Week 5

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:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Tue, 30 Mar 1999 10:02:32 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
On Mar 30, 12:40pm, Gilles Schipper wrote:
> MPEX's criteria for who can do what to what files are well thought out and
> have been used successfully by thousands of users worldwide.
...
> For example, with MPE, a user with SM capability cannot rename a file for
> which he is the creator. But, the SM user can easily find out who the
            v  "not"
> creator is, what the appropriate passwords are for that user, log on as
> that user, even disabling any udc's that affect that user, and ultimately,
> rename the file.

With the POSIX extensions to MPE any user can rename a file as long as they
have DD access to the "from" file's parent directory and CD access to the
target file's parent directory.  Thus, an SM user can rename any file
on the system (PRIV file codes and priv files excepted).

> MPEX's philosophy permits that normally convoluted and indirect function to
> be achievable directly.
>
> I would hope that the new ALTFILE command would emulate MPEX's
> functionality with respect to who can or cannot carry it out.

What are MPEX's rules?

Thanks,
Jeff

--

ATOM RSS1 RSS2