Christian Manivong
a6814ad92e
One script: Get-NetTCPConnection -State Listen, Get-NetUDPEndpoint, the processes holding them and Win32_Service's PIDs. A process running one service names it; a shared svchost runs several, and which of them holds the socket Windows does not say, so it names none. http.sys sockets (WinRM, IIS, SMB) belong to the System process. The fixture is synthetic: no Windows host was at hand. tools/harvest.py records the real output. For netOrk#673.
Synthetic fixtures
These files are what the driver's PowerShell scripts emit, not raw device
output: each script projects its cmdlet results onto flat, primitive fields and
ends in ConvertTo-Json. The shape is therefore this driver's own contract,
and the Python side is tested against it here.
What they cannot prove is that the scripts produce this shape on a real host (property names, Windows PowerShell 5.1 serialisation quirks). They are to be replaced by output recorded from a Windows Server and a Windows 11 client.