HP3000-L Archives

June 1997, Week 3

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 Taffel <[log in to unmask]>
Reply To:
Paul Taffel <[log in to unmask]>
Date:
Thu, 19 Jun 1997 12:47:05 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
  Dear 'Perplexed in Toronto',

  > but how does not having the state-change timestamp initialized cause
  > an mpe fopen security violation for all but AM or greater users?

  I don't think that an uninitialized State-Change field has anything to do
  with security violations.  However, there may be other Posix file-attributes
  that do.  The paper I referred to covers many of these Posix-related issues,
  albeit in a long-winded manner (it was hard to write, it should be hard to
  understand!).

  Try doing a %LISTF ,POSIX on the file(s) in question, followed by a %LISTF
  ,SEC.  You'll probably find that the file either has ACDs assigned that
  restrict access, and/or that its Posix Group field doesn't match the Account
  in which it's located.

  Paul Taffel

______________________________ Reply Separator _________________________________
Subject: RE: What is "state"
Author:  <[log in to unmask]> at Internet-Link
Date:    6/19/97 3:44 PM



Thank you Paul, but how does not having the state-change timestamp
initialized cause an mpe fopen security violation for all but AM or
greater users? The only work around I've found is to release the files
concerned, something my grandmother always told me was a bad idea :-)

John "still wondering" Pickering
JWP Systems Inc.
Toronto

ATOM RSS1 RSS2