nmap / nmap/npcap

Upgrade to Microsoft WHQL Process

Open
#237 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
3.6k
Forks
592
PR merge metrics
No merged PRs in 30d

Description

Microsoft offers their "Windows Hardware Quality Labs" (WHQL) system to help developers build quality drivers. It is critical that we sign up for this because Microsoft will require it in 2021 for drivers. Windows doesn't accept the kind of third party EV codesigning certs we use if the certificate expires after June 20, 2021. Ours expires May 7, 2020. This won't cause a problem for existing Npcap releases made while our cert was valid, but we will be required to have a WHQL signature instead for future releases. WHQL also has other benefits, including an enhanced test suite we can run locally. So we should get this set up well in advance. We will neet to set up a testing server and clients in a local lab (we may be able to use Azure for some of them) and set up testing for the various interfaces/apis we export (device, NDIS filter driver, WFP filter). Then it runs all those tests and produces a report. We take action on any findings until we have a clean report, then we sign that and send it to MS. They send back our driver with their signature on it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the WHQL requirements and mapping the proposed local lab of testing servers and clients to the exported device, NDIS filter driver, and WFP filter interfaces. Done means the test suite runs, findings are resolved, the report is clean, and the resulting driver is submitted for Microsoft's signature.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems, security, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.