http://bugs.winehq.org/show_bug.cgi?id=14334
--- Comment #13 from Forester pbronline-wine@yahoo.co.uk 2008-09-19 13:51:21 --- (In reply to comment #12)
According to MSDN CreateWellKnownSid has been introduced in XP, so installing Win2k SP4 won't help. Any way, not all the tests are skipped, but only those depending on CreateWellKnownSid.
It looks like MS back-ported CreateWellKnownSid() into Win2k SP4 but that's beside the point.
I have added a simple (I mean really dumb) test case that mimics what I think my application does and it passes under Wine and Win2k. So I think I'm ready to submit.
However, I tried calling SetFileSecurity() with the sd returned by GetFileSecurity(). This passes under both Wine and Win2k too. However, my trace in the wine server suggests file_set_sd() bugs out early having hit
/* FIXME: get Unix uid and call fchown */
which just can't be right. I think this arises because I'm using Get & Set FileSecurity. Each call open and closes the file so creating and destroying the file object so, by definition, obj->sd is 0 on entry to file_set_sd(). Ditto for my new dir_set_sd().
Can I still submit the work I've done ?
In the conformance tests, advapi32/tests/security.c, test_GetSecurityInfo() provokes four server calls to file_get_sd(). The (old) tests provoke no server calls to file_set_sd().
The routine test_GetNamedSecurityInfoA() appears to acquire a security descriptor for a directory. This test passes but it does not provoke a server call to my new dir_get_sd() nor a call to the file_get_sd() I began with.