You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ Getting over it will weaponize this already versatile patch, so disabling PatchG
53
53
> [!IMPORTANT]
54
54
> Windows 10 builds are also subject to flight signing, which are code signatures that gets invalid after expiration date, thus preventing system from booting or to be used properly.
55
55
> Getting over this requires additional work (resigning all binaries and disabling integrity checks, or patching bootloader & ci.dll) which is not covered by this project.
56
-
-Works on pre-RTM, post-RTM ("insider") builds are untested but they likely are same as pre-RTM unless KASLR is enabled, which is not supported by this driver.
56
+
-Tested on pre-RTM Windows 10 and early Windows 11 insider builds (i.e. 21390). Builds with security features enabled such as KASLR are not tested.
57
57
58
58
# Usage
59
59
Since TimeDefuser 1.8.3, INF file is deprecated and the driver is instead installed as a service with `sc.exe`. A script for installing named `Installer.bat` will be bundled with subsequent releases.
@@ -102,10 +102,11 @@ These screenshots are all taken by me.
Copy file name to clipboardExpand all lines: TimeDefuser-Research.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -96,6 +96,7 @@ This research is also bundled with a practical Proof-of-Concept (PoC) implementa
96
96
## 7. Threat Model and Abuse Potential
97
97
While this research focuses on expiration enforcement mechanisms, the techniques described are broadly applicable to kernel patching and runtime modification of enforcement logic.
98
98
In a threat context, these routines can be modified to do any arbitrary and potentially malicious activities with a frequency of once per hour.
99
+
99
100
## 8. Responsible Use and Ethical Considerations
100
101
This research is conducted and presented for educational, defensive, and academic purposes. The techniques described are intended to improve understanding of kernel enforcement mechanisms,
101
102
tamper resistance, and system integrity, and to contribute to the broader field of operating system security research.
0 commit comments