Windows Vista added the concept of virtual accounts for services.
There exists a deterministic mapping between the name of a service and its
security identifier.
The format of virtual account's SID is the following.
Revision: 1
Identifier Authority: NT_AUTHORITY (5)
Domain Identifier: NT_SERVICE (80)
Relative Identifier: SHA1(ServiceName)
For example the SID of a service named "TestService" is:
S-1-5-80-3892056402-659729507-4115993473-1921682939-1565901394
RtlCreateServiceSid generates the SID of a service from its name.
This function is the first step towards adding virtual account support to System.Security.Principal.NTAccount from .NET which is required for OculusSetup.exe.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7682
Setting a __wine_x11_focus_time window property to indicate the time of
the last NormalState, -1 if the window is mapping itself, or 0 if the
window is not in a NormalState.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7684
Follow-up of !2786, which appears to have been abandoned.
--
v8: ws2_32/tests: Add test for AF_UNIX sockets.
server: Fix getsockname() and accept() on AF_UNIX sockets.
server: Introduce error when attempting to create a SOCK_DGRAM AF_UNIX socket.
server: Allow for deletion of socket files.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7650
Follow-up of !2786, which appears to have been abandoned.
--
v7: ws2_32/tests: Add test for AF_UNIX sockets.
server: Fix getsockname() and accept() on AF_UNIX sockets.
server: Introduce error when attempting to create a SOCK_DGRAM AF_UNIX socket.
server: Allow for deletion of socket files.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7650
This serie (#5 in PDB rewrite) actually starts the implementation of the i
"new" PDB reader.
Basically, during the phase of migration from the "old" to the "new" PDB
reader, both readers will be used at the same time (for every loaded module
with PDB information).
So:
- be ready to expect an increase in memory usage (as both will handle their
own information),
- in the process of migration, when possible, parts of the "old" reader
will be disabled not to consume too much memory nor time,
Default will be to use the "new" reader. If you really want to use the
"old" reader, set the WINE\_DBGHELP\_OLD\_PDB env variable.
The integration of the "new" PDB reader is done through a set of methods
attached to each debug format (1).
This serie:
- sets the foundations of the "new" PDB reader (in a new pdb.c file),
- use it to support the access to PFO unwinding information in PDB files
(and this allows to unmap the PDB file, used by the all reader, when
all information have been read by "old" reader),
- introduces the methods vtable for each debug format.
Note 1:
- "new" PDB reader will not support as many PDB variations as the "old"
reader,
- actually, PDB files come into two forms. The second form became the
CL.EXE default in MSVC version 8, something like 30 years ago,
(first format was very limited in the potential size of the PDB file),
- also, the CodeView records in the PDB files exist in 3 versions:
+ V1: 2^16 types per image, identifiers as pascal string, 255 char max,
+ V2: 2^32 types per image, identifiers as pascal string, 255 char max,
+ V3: 2^32 types per image, identifiers as C-strings ("unlimited"),
- for now, only support for the V3 CodeView records is included
- I don't plan to add all the other variations as they are very obsolete,
- for the record, this is aligned with clang design decisions for their
PDB implementation,
Note 2:
- "old" reader maps the whole PDB file in memory, then allocate memory
chunks for each internal stream and reconstructs the stream by copying
from the filemap into the stream buffer),
- "new" reader access the PDB file through ReadFile,
[1] dwarf4/5 is a candidate to be moved to this new interface for the
same reasons as PDB (not to load every debug information at module
loading in dbghelp),
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7680
This MR adds an initial implementation of the winsock `WSALookupsService*` methods for performing Bluetooth device discovery (`LUP_CONTAINERS`).
Pending !7472, the code will also eventually support performing device inquiry scans.
--
v15: ws2_32: Implement WSALookupServiceNext for Bluetooth device discovery.
ws2_32: Implement WSALookupServiceBegin for Bluetooth device discovery.
ws2_32/tests: Add tests for the Bluetooth namespace (NS_BTH) in WSALookupServiceBegin/Next.
https://gitlab.winehq.org/wine/wine/-/merge_requests/7542