Skip to content
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

without running test mode! #7

Open
okbach opened this issue Feb 15, 2023 · 1 comment
Open

without running test mode! #7

okbach opened this issue Feb 15, 2023 · 1 comment

Comments

@okbach
Copy link

okbach commented Feb 15, 2023

Can it be used without running test mode in Windows?
I know this is a kind of user protection
But what if I intend to release a version for an ordinary user. Commercial version

@Cassianvale
Copy link

Can it be used without running test mode in Windows? I know this is a user protection but what if I plan to release a version for regular users? Business version

  1. Enable Secure Boot
    1. Use Microsoft WHQL signature
    1. Use driver signature issued in 2013-2015, expired but not revoked or blacklisted (I don't know when a patch will be fixed).
  1. Disable Secure Boot
    1. Use Microsoft WHQL signature
    1. Both sha1 and sha256 with expired signature can run normally
  1. Windows 7
    1. Use Microsoft WHQL signature, SHA256 signature needs patch support (KB3033929).
    1. SHA1 signature
      PS: See how lucky you are to have an expired but not revoked blacklisted SHA1 signature, you can ignore the operating system, sign and run.......
      The above is a reprint

So you must find an EV code signing certificate (must be specified by Microsoft CA company, such as Digicert, application address https://www.ssldun.com/ssl/digicert/csce.html), apply for a Windows Driver Center account, digitally sign the driver and HLK test results

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants