EljakimHerrewijnen/Gupje
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

readme fixes

Browse Source
This commit is contained in:
Eljakim Herrewijnen 2024-12-24 17:16:01 +01:00
parent a31ecd313a
commit fd720273ef
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -2,6 +2,7 @@
Gupje is a bare metal architecture based stub debugger that helps in ``post-exploitation`` steps. Like booting a smartphone after RCE has been achieved. Gupje is also capable of doing ``hardware-in-the-middle`` approaches as well as keeping control over a device while it is booting, this is needed for reaching weird goals like hijacking ``trustzone``. Gupje is a bare metal architecture based stub debugger that helps in ``post-exploitation`` steps. Like booting a smartphone after RCE has been achieved. Gupje is also capable of doing ``hardware-in-the-middle`` approaches as well as keeping control over a device while it is booting, this is needed for reaching weird goals like hijacking ``trustzone``.
Gupje currently supporting the following architectures: Gupje currently supporting the following architectures:
* ARM64 (good support) * ARM64 (good support)
* ARM (minimal) * ARM (minimal)
* ARM Thumb (decent support) * ARM Thumb (decent support)
@ -9,12 +10,13 @@ Gupje currently supporting the following architectures:
The goal is to add support to more targets while I work on them. Because I mainly work on phones this list will probably not grow a lot in the short term. But if you have an interesting target and preferably a way to get into it(RCE), let me know and I will look into it. The goal is to add support to more targets while I work on them. Because I mainly work on phones this list will probably not grow a lot in the short term. But if you have an interesting target and preferably a way to get into it(RCE), let me know and I will look into it.
The only actual things the debugger can do is: The only actual things the debugger can do is:
* Send/Receive (needs to be implemented by the user) * Send/Receive (needs to be implemented by the user)
* Read/Write *some* registers * Read/Write *some* registers
These functions are enough for a processor to run properly. The code size of the debugger is currently smaller than 4096 bytes(depends a bit on user setup) but will probably grow to include 1 extra page to support custom functionality. Like dumping extra registers and more specific processor dependent code. These functions are enough for a processor to run. The code size of the debugger is currently smaller than 4096 bytes(depends a bit on user setup) but will probably grow to include 1 extra page to support custom functionality. Like dumping extra registers and more specific processor dependent code.
In the future it should also be possible to add fuzzing and same architecture rehosting. Once I find a project to implement this at least. In the future it should also be possible to add fuzzing and same architecture rehosting for more advanced fuzzing. Once I find a project to implement this at least.
## Overview ## Overview
A simple overview of how Gupje is meant to be used can be seen below: A simple overview of how Gupje is meant to be used can be seen below: