Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!psinntp!dsh!gary
From: gary@dragon.dsh.org (Gary D. Duzan)
Subject: Re: Porting NetBSD to OS/2 and Windows NT
Organization: Delaware State Hospital
References: <2cgabn$t3n@scunix2.harvard.edu> <pcbsdCGuzuK.FF5@netcom.com> <2cpjp3$k89@u.cc.utah.edu>
Message-ID: <CGw83t.3K3@dragon.dsh.org>
Date: Mon, 22 Nov 1993 12:31:04 GMT
Lines: 29
In article <2cpjp3$k89@u.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:
=>
=>From personal experience trying to pack data into file systems that
=>weren't designed with the ability to add to the information associated
=>with a file, and that fact that ownership and permissions, etc. are
=>normally stored as file attributes in the inode in BSD FFS and similar
=>file systems, I'd hazard a guess that everything there in FFS but not
=>there in OS/2 will become one of:
=>
=>1) A field in a single extended attribute.
=>
=>2) An extended attribute (one per item).
=>
Mightn't such an approach cause security problems for programs
which assume the system is honoring the file ownership and permissions?
I would think that OS/2 programs would be able to access the files
regardless of the extended attributes, unless the files have some
other protection. /etc/master.password is one example.
Gary D. Duzan
Humble Practitioner of the Computer Arts
--
gary@dsh.org
_o_ ------------ _o_
[|o o|] First things first, but not necessarily in that order. [|o o|]
|_O_| Disclaimer: I have no idea what I am talking about. |_O_|