From 32d6e1cb045860f3194c097547eaf6482b83c0d9 Mon Sep 17 00:00:00 2001
From: Vladimir Stoilov <github@pendsv.com>
Date: Tue, 28 Jan 2025 11:46:15 +0200
Subject: [PATCH] [kext] Fix dev build documentation
---
windows_kext/README.md | 26 ++++++++++----------------
windows_kext/link-dev.ps1 | 21 +++++++++++++++++++++
2 files changed, 31 insertions(+), 16 deletions(-)
create mode 100644 windows_kext/link-dev.ps1
diff --git a/windows_kext/README.md b/windows_kext/README.md
index ce80d0b1..0e4daa80 100644
--- a/windows_kext/README.md
+++ b/windows_kext/README.md
@@ -1,7 +1,7 @@
# Portmaster Windows kext
Implementation of Safing's Portmaster Windows kernel extension in Rust.
-### Documentation
+### Documentation
- [Driver](driver/README.md) -> entry point.
- [WDK](wdk/README.md) -> Windows Driver Kit interface.
@@ -9,8 +9,7 @@ Implementation of Safing's Portmaster Windows kernel extension in Rust.
- [Release](release/README.md) -> Guide how to do a release build.
- [Windows Filtering Platform - MS](https://learn.microsoft.com/en-us/windows-hardware/drivers/network/roadmap-for-developing-wfp-callout-drivers) -> The driver is build on top of WFP.
-
-### Building
+### Building (For testing and development)
The Windows Portmaster Kernel Extension is currently only developed and tested for the amd64 (64-bit) architecture.
@@ -53,23 +52,18 @@ __Build driver:__
```sh
cd driver
- cargo build
+ cargo build --release
```
> Build also works on linux
__Link and sign:__
-On a windows machine copy `driver.lib` form the project target directory (`driver/target/x86_64-pc-windows-msvc/debug/driver.lib`) in the same folder as `link.bat`.
-Run `link.bat`.
+On a windows machine copy `driver.lib` from the project target directory (`driver/target/x86_64-pc-windows-msvc/release/driver.lib`) in the same folder as `link-dev.ps1`.
+Run `link-dev.ps1`.
-`driver.sys` should appear in the folder. Load and use the driver.
+`driver.sys` should appear in the folder.
-### Test
-- Install go
- - https://go.dev/dl/
-
-```sh
- cd kext_tester
- go run .
+Sign the driver with the test certificate:
```
-
-> make sure the hardcoded path in main.go is pointing to the correct `.sys` file
+ SignTool sign /v /s TestCertStoreName /n TestCertName driver.sys
+```
+Load and use the driver.
diff --git a/windows_kext/link-dev.ps1 b/windows_kext/link-dev.ps1
new file mode 100644
index 00000000..39ba4e3d
--- /dev/null
+++ b/windows_kext/link-dev.ps1
@@ -0,0 +1,21 @@
+# Example script for creating debug builds. Libraries may change depending on the version of the WDK that is installed.
+
+$SDK_Version = "10.0.26100.0"
+
+link.exe /OUT:driver.sys `
+/MANIFEST:NO /PROFILE /Driver `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\wdmsec.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\ndis.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\fwpkclnt.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\BufferOverflowK.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\ntoskrnl.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\hal.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\$SDK_Version\km\x64\wmilib.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\wdf\kmdf\x64\1.15\WdfLdr.lib" `
+"C:\Program Files (x86)\Windows Kits\10\lib\wdf\kmdf\x64\1.15\WdfDriverEntry.lib" `
+ "driver.lib" `
+/RELEASE /VERSION:"10.0" /DEBUG /MACHINE:X64 /ENTRY:"FxDriverEntry" /OPT:REF /INCREMENTAL:NO /SUBSYSTEM:NATIVE",6.01" /OPT:ICF /ERRORREPORT:PROMPT /MERGE:"_TEXT=.text;_PAGE=PAGE" /NOLOGO /NODEFAULTLIB /SECTION:"INIT,d"
+
+if(!$?) {
+ Exit $LASTEXITCODE
+}