Contact person: Windows driver that simulates a specific hardware button press

Phone:Show

Email:Show

Location: Israel

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Objective
Build a signed Windows driver that programmatically simulates a specific hardware button press, so that Windows reliably performs the operation that would happen if a user had clicked the actual keyboard key.
Scope & Approach
• Implement a KMDF driver that exposes a secure control interface (IOCTL/Device Interface).
• Preferred mechanism: present a virtual HID “System Control” device and inject the desired key usage (HID Usage Page: Generic Desktop, Usage: TBD), which Windows handles like a physical key.
• Must work on Windows 10/11 (x32 and x64);
• Include a small admin test tool/PowerShell script to trigger the key press via the driver.
Responsibilities
• Design & implement the KMDF driver (Visual Studio + WDK).
• Create INF/CAT and installation package; support PnPUtil install/uninstall.
• Implement security controls: that only a certain application using a certain usage pattern (TBD) can trigger the action; validate the caller.
• Provide ETW/event logging for actions and errors.
• Handle edge cases: TBD during project initiation
• Thorough testing: verify action and no crashes on rapid repeat.
• Documentation: build, install, usage, troubleshooting, security model.
Deliverables
• Source code (C/C++, KMDF), build scripts, and solution files.
• Signed driver package (attestation or WHQL/HLK path).
• Admin CLI/GUI tool (or PowerShell module) that sends the trigger to the driver.
• Test report: OS versions, coverage, negative tests (blocked by policy).
• Maintenance notes: how to update the certificate/signing and re-package.
Acceptance Criteria
• On supported hardware, invoking the provided tool causes the system to perform the desired task within policy limits.
• No kernel crashes, verifier clean, no Code Integrity violations.
• Driver passes KMDF Verifier and relevant HLK tests for HID/virtual device class.
• Uninstall leaves the system clean (no ghost devices, no lingering services).
Qualifications
• 5+ years with Windows kernel development (KMDF) and driver signing.
• Experience with HID/Virtual HID Framework (VHF) or virtual input devices.
• Strong understanding of Windows power states (S0/S3/S4), ACPI, and UAC/Code Integrity.
• Familiarity with HLK, ETW, WinDbg, and Driver Verifier.
Nice to Have
• Experience delivering drivers via attestation signing and EV code signing.
• Support for ARM64 build target.
• Optional: a UMDF helper service for policy checks/telemetry.
Constraints & Notes
• No undocumented kernel calls to force the operation; solution must rely on supported pathways (e.g., virtual HID []).
• Must fail gracefully if system policy disallows the specific action and log the reason.
• Ensure minimal attack surface; validate all IOCTLs and reject non-approved callers." (client-provided description)