|
You are here |
blog.malwaremustdie.org | ||
| | | | |
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... | |
| | | | |
g-w1.github.io
|
|
| | | | | See part 2 for this post here | |
| | | | |
shrik3.com
|
|
| | | | | [AI summary] The user provided a detailed explanation of dynamic linking in the context of ELF binaries, covering topics such as the ELF format, symbol resolution, the dynamic linker, and various tools and functions involved in the process. They also mentioned other resources for further reading and included some additional content about the a.out format and other programming concepts. The user's message seems to be a comprehensive overview of dynamic linking and related topics, possibly for educational or reference purposes. | |
| | | | |
intezer.com
|
|
| | | This deep dive aims to guide you through .NET reverse engineering, equipping you with the essential knowledge to analyze .NET malware. | ||