Win32 port

[Peter Kümmel]

Havoc Pennington wrote:
> Tor Lillqvist wrote:
>> Havoc Pennington writes:
>>  > (Am I just missing that part of the patch?) What I'm wondering is
>>  > how does it get allocated/freed.
>>
>> If I recall correctly what my patch did, the string representation of
>> a SID is allocated whenever a SID the code hasn't seen before needs
>> handling, and is never freed. Kinda like a quark.
>>
> 
> Is this done in a dbus-specific hash table or by the Windows API? If
> we're keeping a dbus hash table anyway, then we could do it _exactly_
> like GQuark ... which would give us an integer that could simply be
> stuffed in dbus_uid_t as it stands, without having to change anything.
> 
> Any idea what the windows API calls involved are here so I can read the
> docs on those?
> 
> Havoc
> 
> 

Currently the char* is used as key (therfore my first patch):

_dbus_hash_table_insert_string (win32_sids, string, string);

And here a link to the msvc docs:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secauthz/security/convertsidtostringsid.asp

Peter