[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: wineserver: Added support for read/only Registry,
From:       Alexandre Julliard <julliard () winehq ! org>
Date:       2009-11-30 15:43:13
Message-ID: 871vjg9fxq.fsf () wine ! dyndns ! org
[Download RAW message or body]

Paul Chitescu <paulc@voip.null.ro> writes:

> In the filesystem we use as backend for Registry all we can tell is if we can 
> write to it or not so in the end one bit is all that's relevant (except if 
> it's completely unreadable when wine should abort).
>
> No matter what an user does it cannot change that. We don't want a wine 
> service running as root trying to replicate Windows access rights on the 
> native system, do we?

Yes, the right approach to multiuser is to have wineserver and system
processes run as root, and normal processes run as different users.

-- 
Alexandre Julliard
julliard@winehq.org


[prev in list] [next in list] [prev in thread] [next in thread]