Just to clarify, I think most of the work in the SRM to support
multiple users is already in place.
This isn't to say that the SRM is complete, it isn't. It's mostly just
token handling and security descriptors which are implemented at the
moment.
We still need support for ACLs and access state.
The current code needs an overhaul to bring it up to the standard of
the rest of the kernel.
Ged.
(SeAccessCheck & co). Actually, my first idea was
to looking for what is
missing in this executive component for multiuser purpose. The best for me
would be to know what exactly is not implemented yet. I talked with
GedMurphy on IRC and he helped a lot. According to him, a standard
implementation already exists. But it needs to be improved a lot before
being multiuser capable. I will take a deep look at existing implementation
on RoS, and compare it to different sources as GedMurphy suggested to me.
Apart the executive component, what other components should be improved ?
Thank you
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev