[spam-high] Re: [PATCH 3/7] advapi: Implement GetNamedSecurityInfoW on top of GetSecurityInfo (try 3).

Erich E. Hoover ehoover at mymail.mines.edu
Mon Nov 5 16:14:26 CST 2012

On Mon, Nov 5, 2012 at 12:41 PM, Charles Davis <cdavis5x at gmail.com> wrote:
> ...
> I can name at least four: registry keys (HKEY), services (SC_HANDLE), window stations (HWINSTA), and desktops (HDESK). On native, all those types of objects are protected with ACLs, and all those types have unique functions for manipulating them. But you don't have to worry about that for now; just supporting file-like objects is fine right now, especially since Wine only supports one user per prefix right now, so objects that exist in the file-system are the only ones where we have to worry about other users. (Besides, Wine probably doesn't even support multiple window station and desktop objects anyway...)
> Sorry for the noise.

Quite alright, you make good points.  Since I just defended my
dissertation this morning, I can now focus on this more intensely.  I
honestly should have thought of the registry keys at the very least,
but for some reason that thought escaped me.  Previously
GetNamedSecurityInfo just blanket returned world access rights which,
to me, is really masquerading as a semi-stub and hiding a host of
unsupported features.  At this point it would probably be better to
break a few apps by failing utterly than silently succeed, that way we
can determine what we need to implement.


More information about the wine-devel mailing list