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:
Paul Courry <[log in to unmask]>
Reply To:
Paul Courry <[log in to unmask]>
Date:
Tue, 30 Mar 1999 01:57:26 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
On item 2, suggest you restrict non-SM to any file they are the Creator of. Otherwise there is too much potential for mischief on
the part of a disgruntled employee.

If you do leave 2 as is, please make sure you change the modification and access dates so we can detect and backout any
malicious damage. In fact, please do that no matter how this turns out.

Paul Courry

On Mon, 29 Mar 1999 21:52:32 -0800, Jeff Vance wrote:

>Hi all,
>
>We *may* enhance the ALTFILE CI command so that a user can modify a
>file's file code.  If we do this here are my thoughts on the
>restrictions on ALTFILE:
>
>  1. SM can alter any file's file code to any value (even negative)
>
>  2. Non-SM can alter any file he/she has WRITE access to, to a file
>     code whose numeric value is >= 0.
>
>  3. Non-SM cannot alter a file with a negative (PRIV) file code to
>     any file code value.
>
>Thanks in advance for your thoughts.
>
>Jeff Vance, CSY
>
>--
>

ATOM RSS1 RSS2