Topic

about hck test

Tagged: 

Viewing 15 posts - 1 through 15 (of 20 total)
1 2
  • Author
    Posts
  • August 19, 2024 at 4:29 am #13824
    kahotv
    Participant

    To run on systems such as Win7 and Win8, it is necessary to undergo HCK testing. Do you have any relevant information? Or do you provide this service?

    August 19, 2024 at 10:48 am #13825
    Vadim Smirnov
    Keymaster

    Have you encountered any issues installing Windows Packet Filter or WireSock on Windows 7/8? While HCK/WHQL certification is beneficial, it is not required.

    August 20, 2024 at 10:46 am #13831
    kahotv
    Participant

    The sys file I compiled myself did not undergo HCK testing and was submitted to Microsoft for signature using. cab. It can run normally on the Windows 10/11 platform, but it prompts that the signature is invalid on Windows 7/8.

    • This reply was modified 2 years, 1 month ago by kahotv.
    August 20, 2024 at 10:46 am #13832
    kahotv
    Participant

    The sys provided by you can run successfully

    • This reply was modified 2 years, 1 month ago by kahotv.
    August 20, 2024 at 10:48 am #13835
    kahotv
    Participant

    On Win7/8, the sys I compiled myself can run successfully after disabling the system’s signature verification.

    • This reply was modified 2 years, 1 month ago by kahotv.
    August 20, 2024 at 1:49 pm #13838
    Vadim Smirnov
    Keymaster

    Driver signing can be challenging, but in my experience, token-based certificates from GlobalSign typically work without any issues for Windows 7/8.

    August 21, 2024 at 4:35 am #13841
    kahotv
    Participant

    I have a sha256 EA certificate, and the process is to compile it ->package it into. cab (only sign cab, not sys inside) ->submit it to “partner.microsoft.com”, download it back and attach a signature to sys. Is there a problem with this step? According to this process, netfiltersdk runs well on Win7/8/10/11, but ndisrd only runs on Win10/11, so I suspect HCK testing is needed.

    August 21, 2024 at 4:46 am #13842
    kahotv
    Participant

    The last step cannot be done without additional signatures (only retaining Microsoft signatures)

     

    https://partner.microsoft.com/en-us/dashboard/hardware/driver/

    Select All

    Requested Signatures
    Windows 10 Client versions 1506 and 1511 x64 (TH2)
    Windows 10 Client version 1607 x64 (RS1)
    Windows 10 Client version 1703 Client x64 (RS2)
    Windows 10 Client version 1709 Client x64 (RS3)
    Windows 10 Client version 1709 Client ARM64 (RS3)
    Windows 10 Client version 1803 Client x64 (RS4)
    Windows 10 Client version 1803 Client ARM64 (RS4)
    Windows 10 Client version 1809 Client x64 (RS5)
    Windows 10 Client version 1809 Client ARM64 (RS5)
    Windows 10 19H1 Client x64
    Windows 10 19H1 Client ARM64
    Windows 10 Client version 2004 x64 (Vb)
    Windows 10 Client version 2004 ARM64 (Vb)
    Windows – Client, version 21H2 x64 (Co)
    Windows – Client, version 21H2 ARM64 (Co)
    Windows 11 Client, version 22H2 x64 (Ni)
    Windows 11 Client, version 22H2 ARM64 (Ni)
    Windows 11 Client, version 24H2 x64 (Ge)
    Windows 11 Client, version 24H2 ARM64 (Ge)

    August 21, 2024 at 5:04 am #13843
    kahotv
    Participant

    My signature process may be non-standard, can you tell me about your signature process?

    August 21, 2024 at 12:00 pm #13844
    Vadim Smirnov
    Keymaster

    For Windows 10/11, you’re following the correct process. Though I sign the driver binary before submitting it to MS. However, for Windows 7/8, it’s sufficient to sign the driver with just your code signing certificate.

    August 22, 2024 at 5:07 am #13852
    kahotv
    Participant

    Thank you, I succeeded! I just realized that sha1 signatures can still be used now.I don’t need an HCK test now.

    August 22, 2024 at 5:14 am #13853
    kahotv
    Participant

    The main reason is that the CA of my certificate is not in the system’s trusted list and needs to be manually imported. I mistakenly thought that HCK testing was needed.

    August 22, 2024 at 9:44 am #13854
    Vadim Smirnov
    Keymaster

    I’m glad you were able to identify the issue and resolve it successfully. 👍

    August 22, 2024 at 10:02 am #13856
    kahotv
    Participant

    Excuse me, did the ndisrd demo not use HCK testing? It works successfully on Win7/8, but mine will prompt that the signature is invalid. Error 577 is reported when executing the command ‘sc start ndisrd’.

    August 22, 2024 at 11:10 am #13857
    Vadim Smirnov
    Keymaster

    You’re correct, I did not pass the Windows 7/8 driver through HCK testing, and as you may have noticed, it doesn’t have a Microsoft signature.

  • Author
    Posts
Viewing 15 posts - 1 through 15 (of 20 total)
1 2
  • You must be logged in to reply to this topic.