From b6ffad608612319d7c512952019fdcc3f660752d Mon Sep 17 00:00:00 2001 From: "Mariusz B. / mgeeky" Date: Mon, 27 Sep 2021 11:19:52 +0200 Subject: [PATCH] readme --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 81a1c33..36faab3 100644 --- a/README.md +++ b/README.md @@ -12,6 +12,8 @@ Especially demonstrated in this video: [Nighthawk - Thread Stack Spoofing](https://vimeo.com/581861665) +**A note on wording** - some may argue that the technique presented in this implementation is not strictly **_Thread Stack Spoofing_** but rather _Call Stack Spoofing_ to some extent. +I myself believe, that whatever wording is used here, the outcome stays similar to what was presented in an originally named technique - thus the borrowed name for this code. Since we're clobbering some pointers on the thread's stack, wouldn't we call it spoofing the stack anyway and ultimatley still resort to - _Thread Stack Spoofing_? The answer is left to the reader. ## How it works?