-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Github Actions workflow to create exe/msi package, with valid driver signature #6
Comments
I'm curious to see how you get the driver's certificate. Do you need to pay something to Microsoft every year? |
Hi @bpetit, is there an ETA when the driver will be signed, and therefore easier to deploy as an msi/exe? |
Hi, It's a matter of days now |
@TheElectronWill yes you need to pay for an EV certificate with a microsoft partner, then sign an hlkx archive you get from hlk studio running tests on your driver, then send it to MS. It was a long journey, I'll try to document that somewhere. |
Does this mean that Hubblo/Scaphandre or the community will not provide a signed installer for the driver to use everywhere? |
We will provide for sure an installer containing both scaphandre and the signed driver (exactly like Intel Power Gadget that includes a userland software and a signed driver). We will also (and just did on the 0.0.4 release page) publish the signed .sys/.cat files of the driver (+unsigned .inf file), that anyone could embed in an installer. Providing a package with only the driver inside is not a priority however, but forking the iss config file available in the scaphandre repository one could make a new iss config only embedding the driver and create a specific installer. |
Thanks @bpetit. |
Procedure to sign the driver has been validated.
We now have to:
The text was updated successfully, but these errors were encountered: