Explore >> Select a destination
|
You are here 
|
blog.pkh.me | ||
| | | | |
chovid99.github.io
|
|
| | | | | Security's blog made by Chovid99 | |
| | | | |
0x434b.dev
|
|
| | | | | This is a write-up for solving the devils-swapper RE challenge.?? It was mostly intended for my personal archive, but since it may be interesting to all of you. This especially applies if you're still rather new to the whole RE world, as the write-up turned out to be quite verbose. | |
| | | | |
www.lukas-barth.net
|
|
| | | | | This article explores how to exploit side effects during dynamic initialization. It gives an overview over how dynamic initialization works in a typical C++ executable on Linux. | |
| | | | |
www.caichinger.com
|
|
| | | Introduction ELF is the file format used for object files (.o's), binaries, shared libraries and core dumps in Linux. It's actually pretty simple and well thought-out. ELF has the same layout for all architectures, however endianness and word size can differ; relocation types, symbol types and the like may have platform-specific values, and of course the contained code is arch specific. An ELF file provides 2 views on the data it contains: A linking view and an execution view. Those two views can be accessed by two headers: the section header table and the program header table. Linking view: Section Header Table (SHT) The SHT gives an overview on the sections contained in the ELF file. Of particular interest are REL sections (relocations), SYMTAB/DYNSYM (sym... | ||
