| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
This is the start of an overarching change meant to simplify sploit
library imports. In general, all packages (directories) are intended to
export all the classes, methods, and variables of their contained
modules. This way users need only import the package, which leads to
less verbose import statements (and usually fewer import statements).
We would still like to gate objects behind their respective packages,
rather than providing the whole world with `from sploit import *` so
that users can still have some amount of control over what is brought
into their global namespace.
Beware: For code internal to sploit, full module imports should probably
continue to be used. Otherwise, there is a possibility for circular
imports if two modules from two packages cross import.
Signed-off-by: Malfurious <m@lfurio.us>
|
|
This new class is intended to be used to return data from gadget
searches, and is able to be nested within object Symtbls.
Signed-off-by: Malfurious <m@lfurio.us>
Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
|
|
Create a class which encapsulates some basic information about an ELF
file and provides a convenient interface for basic reverse engineering.
In particular, ELF automatically loads the symbol table of the given elf
file and recursively creates ELF objects for any linked libraries.
Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
|
|
Add an r2 module with several helper functions that do a number of
simple reverse engineering tasks to aid in writing simple sploit
scripts. The functions in this module invoke radare2 to accomplish their
tasks.
Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
|
|
add helper function to invoke ldd to get a list of libraries that will
be linked to a given ELF
Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
|
|
Signed-off-by: dusoleil <howcansocksbereal@gmail.com>
|
