home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!gumby!wupost!cs.utexas.edu!tamsun.tamu.edu!bdubbs
- From: bdubbs@cs.tamu.edu (Bruce Dubbs)
- Subject: Re: OS/2 Needs a Supervisor mode!
- Message-ID: <1992Aug16.161525.23512@tamsun.tamu.edu>
- Sender: news@tamsun.tamu.edu (Read News)
- Organization: Computer Science Department, Texas A&M University
- References: <1992Aug15.011002.25592@microsoft.com> <1992Aug15.230755.14630@chpc.utexas.edu> <1992Aug16.001819.14010@unixg.ubc.ca>
- Date: Sun, 16 Aug 1992 16:15:25 GMT
- Lines: 31
-
- In article <1992Aug16.001819.14010@unixg.ubc.ca> ochealth@unixg.ubc.ca (ochealth) writes:
- >
- >Well, some people have complained about OS/2 not having multiuser capabilities
- >out of the box, but I think IBM should include a "Supervisor" or "root"
- >mode, and a "User" mode as a bare minimum. A "restricted" mode would also
- >be nice.
- >
- >Right now, it is easy for a Trojan Horse program to destroy a system;
- >it is easy for a buggy program or a novice user to cripple the system.
- >I can also think of a conceivable, albeit difficult way for a virus to spread.
- >
- >Right now, any program can modify the Config.sys file. It would be better
- >to require a password supervisor mode to edit config.sys, delete/change
- >dll and other drivers etc.
-
- Why don't you just make CONFIG.SYS read only using the ATTRIB command?
- Ditto for the .dll's. This may not be a perfect solution, but since
- OS/2 traps I/O, a program cannot bypass it and manipulate the hardware
- directly.
-
- >[stuff deleted]
-
- -- Bruce
-
-
-
-
- --
- Bruce Dubbs | Oxymorons of note:
- bdubbs@neuron.tamu.edu | Honest Politician, Political Science,
- bdubbs@sadis01.sa.aflc.af.mil | Scrupulous Lawyer
-