Timeline for Modifying Windows DLLs
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2022 at 7:19 | comment | added | 0xC0000022L♦ | Some of those DLLs seem to be hardcoded these days (I suppose into the smss binary or so). Point being that the registry isn't the sole source for the setting of what DLL is a known DLL. | |
| Feb 10, 2017 at 20:10 | comment | added | NirIzr | Yes. I mentioned that in my original answer. These approaches answer OPs original request: a easy way that will not require hooking, and I would think is perfectly fine when done in a VM or as part of a one time limited test (as is implied by OPs POC remark). | |
| Feb 10, 2017 at 20:03 | comment | added | peter ferrie | yes, but (1) and (2) are ugly hacks that have system-wide implications, like visiting someone's house and changing their carpet. The changes should be limited to the current process. | |
| Feb 8, 2017 at 11:21 | history | edited | NirIzr | CC BY-SA 3.0 |
added 392 characters in body
|
| Feb 8, 2017 at 11:12 | history | answered | NirIzr | CC BY-SA 3.0 |