From b5620cc252ff0d84812716a1fed66875b30a0d74 Mon Sep 17 00:00:00 2001 From: Elliot Killick Date: Tue, 31 Oct 2023 10:26:55 +0000 Subject: [PATCH] Cleanup --- .../{LdrLockLiberator.c => LdrLockLiberatorWDK.c} | 0 LdrLockLiberatorWDK/Sources | 2 +- README.md | 2 +- 3 files changed, 2 insertions(+), 2 deletions(-) rename LdrLockLiberatorWDK/{LdrLockLiberator.c => LdrLockLiberatorWDK.c} (100%) diff --git a/LdrLockLiberatorWDK/LdrLockLiberator.c b/LdrLockLiberatorWDK/LdrLockLiberatorWDK.c similarity index 100% rename from LdrLockLiberatorWDK/LdrLockLiberator.c rename to LdrLockLiberatorWDK/LdrLockLiberatorWDK.c diff --git a/LdrLockLiberatorWDK/Sources b/LdrLockLiberatorWDK/Sources index 4427b01..3dce213 100644 --- a/LdrLockLiberatorWDK/Sources +++ b/LdrLockLiberatorWDK/Sources @@ -43,4 +43,4 @@ USE_MSVCRT=1 # The C standard that comes with this WDK version is very old: C89 (very broken in terms of compliance) # For further development, I recommned switching to C++ (change this to a .cpp/.cc file) -SOURCES=LdrLockLiberator.c +SOURCES=LdrLockLiberatorWDK.c diff --git a/README.md b/README.md index b32178c..842348e 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ It's exactly what it sounds like. Unlock Loader Lock, set loader events, and fli ### Escaping at the Exit -We use the CRT `atexit` typically used by EXEs in our DLL code to escape Loader Lock when the program exits. For dynamic loads, this is made 100% safe by pinning (`LDR_ADDREF_DLL_PIN`) our library using `LdrAddRefDll` so a following `FreeLibrary` won't remove our DLL from memory. +We use the CRT `atexit` typically used by EXEs in our DLL code to escape Loader Lock when the program exits. For dynamic loads (using LoadLibrary), this is made 100% safe by pinning (`LDR_ADDREF_DLL_PIN`) our library using `LdrAddRefDll` so a following `FreeLibrary` won't remove our DLL from memory. ### Using Locks to Our Advantage