/explore
|
You are here 
|
alice.climent-pommeret.red | ||
| | | | |
oldboy21.github.io
Ciao World, since I can't get enough of playing around with the Reflective DLL that inspired the very first blog during the Christmas Holiday, after the YOLO Loader I decided to grant the little nasty DLL a new super-power: Indirect syscalls So what I will be addressing here is: Indirect syscall: why and (mostly) references SSN enum and PIC challenges 1 tb of MASM Disclaimer I write code and implement techniques for research and learning purposes only. |
|
| | | | | ||
| | | | |
redops.at
|
|
| | | | | ||
| | | | |
keyj.emphy.de
[AI summary] The article discusses the process of creating ultra-small Windows executables by optimizing the PE (Portable Executable) format. KeyJ, the author, details various techniques such as removing sections, collapsing headers, and using hash-based import lookups to minimize the executable size. The article also includes comments from readers discussing the challenges and successes of these optimizations, as well as the importance of compatibility across different Windows versions. The final executable size is reduced to around 268 bytes, and the author acknowledges the trade-offs between size and compatibility. |
|
| | | | | ||
| | | | |
patshaughnessy.net
[AI summary] The article discusses the process of learning to read x86 assembly language, focusing on how it can be a useful skill for understanding low-level operations of microprocessors. It outlines the challenges of reading assembly, especially in debugging scenarios, and provides an example of translating Ruby code into x86 assembly using Crystal. The article also explains the syntax and structure of x86 assembly, including register usage, instruction suffixes, and the differences between AT&T and Intel syntax. It highlights the complexity of x86 assembly due to its historical evolution and the need for understanding register sizes and operand notation. |
|
| | | |||
