-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viosock: Remove Coinstaller Stuff from the INF File #1064
base: master
Are you sure you want to change the base?
Viosock: Remove Coinstaller Stuff from the INF File #1064
Conversation
175e5cf
to
f6c448c
Compare
Is the protocol not registered? |
It is not. I think the INFs were not responsible for registering it even before this PR (I did not notice such registrations). I can of course test this (old INFs) on a fresh machine. |
[VirtioSocket_Device_CoInstaller_AddReg] |
Ah, OK, I missed that. I will improve the PR. |
@@ -26,7 +26,7 @@ DriverPackageDisplayName = %VirtioSocket.DeviceDesc% | |||
PnpLockdown = 1 | |||
|
|||
[DestinationDirs] | |||
DefaultDestDir = 12 | |||
DefaultDestDir = 13 | |||
VirtioSocket_Lib_CopyFiles = 11 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to https://learn.microsoft.com/en-us/windows-hardware/drivers/develop/run-from-driver-store#other-files, you should also move VirtioSocket_Lib_CopyFiles to 13. Please check if is this possible or not. This does not work for RNG providers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will look into it, thanks. Yes, I know about RNG.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@MartinDrab Please look into changes in #1075
HLK for 2022 and attestation signing fails with DIRID13 and without TargetOS decoration
Signed-Off-By: Martin Drab <martin.drab@virtuozzo.com>
9191b70
to
cf7e51a
Compare
…irectory Signed-Off-By: Martin Drab <martin.drab@virtuozzo.com>
Signed-Off-By: Martin Drab <martin.drab@virtuozzo.com>
cf7e51a
to
78422de
Compare
Signed-Off-By: Martin Drab <martin.drab@virtuozzo.com>
aff12c4
to
96d9493
Compare
Let's test how well this passes through HCK/HLK. If this approach proves working, let's add an installer app and an Uninstall key. Signed-Off-By: Martin Drab <martin.drab@virtuozzo.com>
96d9493
to
33760a4
Compare
@@ -56,6 +55,15 @@ WdfCoInstaller$KMDFCOINSTALLERVERSION$.dll = 1 ; make sure the number matches wi | |||
[VirtioSocket_Device.NT] | |||
CopyFiles=Drivers_Dir,VirtioSocket_Lib_CopyFiles | |||
|
|||
[VirtioSocket_Device.10.0.15063.Software] | |||
AddSoftware=WSKWSP,,VirtioSocket_Software |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-
How do you expect to sign this driver for Windows Server 2016? After applying a Cumulative Update for Windows Server 2016 for x64-based Systems (KB4598243), the latest OS Build is 14393.4169.
-
According to https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-addsoftware-directive:
Each AddSoftware directive describes the installation of standalone software. This directive should be used in an INF file of the **SoftwareComponent** setup class.
How will this work in this INF withClass=System
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- It seems that the
SoftwareComponent
class is not a requirement. For example, INF for NVDA Display Driver on my machine uses theAddSoftware
directive but is of classDisplay
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- well, I suppose there need to be special INF sections for handling OS versions that do not support the
AddSoftware
directive. I am currently experimenting with this.
Unfortunately, it is not possible to register the Winsock Provider by just adding certain keys and values into the Registry (like inviorng
case); theAddReg
directive is not strong enough for that.
SoftwareType=1 | ||
SoftwareBinary=viosocklib-test.exe | ||
SoftwareArguments="/i" | ||
SoftwareVersion=1.0.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this version be equal to the driver version or the binary version?
The driver is installed in the Driver Store (DIRID 13) instead of the System Drivers directory (DIRID 12).