[openbeos] Re: Singleuser vs Multiuser
- From: "Michael Phipps" <mphipps1@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 15 Dec 2001 13:53:34 -0500
OK. This thread has gone on a long time.
Basically, I see three options:
1) BeOS as is. There are no logins and everyone can access every file.
2) BeOS with the EXISTING file permissions used. Groups and users already
exist. Basically this would consist of adding a decent login program that is at
least quasi-secure. Asks for name and password. Logs you in and gives you your
own home directory. Users could not touch other users home directories or
anything in them unless the permissions were changed. This would NOT involve
any API changes or give you "REAL" security - apps that belong to one user
could still hack into another users running apps. Basically, this is a one user
at a time multi-user system.
3) Features of 2, except changing the API's to check security such that the
system is more secure. Multiple people can be running apps and be certain that
no one else can see their apps memory space. BMessages check who they are from.
(With BeOS scripting, you could ask user joe's copy of gobe to send you the
text he is working on).
PERSONALLY, I am leaning toward 2, with 1 being an option at login. My personal
machine is MINE and no one else is allowed on. But I can see that there are
families that share machines, so 2 has a place. Universities, ditto. But 3 is
really for machines that are shared by people at the same time. And that is, I
think, more than we want to bite off. Certainly for the forseeable future.
Maybe ever. Also note that #1 is all that is required for R1.
Other related posts:
