peda VS RsaCtfTool

Looks like they are using PEDA.

There are a lot of these types of tools already in the reverse engineering community (in order of lowest chance of breaking when you throw really weird stuff at it):

GEF: https://gef.readthedocs.io/en/master/

PWNDBG: https://github.com/pwndbg/pwndbg

PEDA: https://github.com/longld/peda

They also come with a slew of different features to aid in RE/exploit dev, but many of them are also useful for debugging really weird issues.

PEDA - GDB plugin (only python2.7).

peda - Python Exploit Development Assistance for GDB.

Did you follow the instructions? Step 2 adds PEDA to your ~/.gdbinit so it will/should load every time you open gdb. So if it doesn't work check your ~/.gdbinit file.

Appreciate your insight! After a quick search I found this one https://github.com/RsaCtfTool/RsaCtfTool . Probably gonna give it a try

To check some base vulnerabilities you can use https://github.com/Ganapati/RsaCtfTool

RSACTFTool - A tool for recovering RSA private keys with various attacks.

RsaCtfTool - Decrypt data enciphered using weak RSA keys, and recover private keys from public keys using a variety of automated attacks.

Normally, it is better to implement the RSA cryptosystem and solve the problem, but in actual CTF, it is necessary to solve the problem as fast as possible, and in this article, we will use RsaCtfTool(https://github.com/Ganapati/RsaCtfTool ), which can solve the RSA cryptosystem quickly in CTF. In this article, we will use RsaCtfTool, which can solve RSA cryptosystem quickly by CTF. It is very simple to use, just give c, n, and e as optional arguments, and the plaintext will be returned.