Explore >> Select a destination
|
You are here 
|
venam.net | ||
| | | | |
blog.nuculabs.dev
|
|
| | | | | Hello, In this article I'll present you my solution on the Chapter 5 CTF from the book Practical Binary Analysis. For this binary, the hint is to fix four broken things. Running file gives us the following response: 1 2 binary@binary-VirtualBox:~/ctf$ file ./lvl3 ./lvl3: ERROR: ELF 64-bit LSB executable, Motorola Coldfire, version 1 (Novell Modesto) error reading (Invalid argument) And the readelf command gives us: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 binary@binary-VirtualBox:~/ctf$ readelf -h ./lvl3 ELF Header: Magic: 7f 45 4c 46 02 01 01 0b 00 00 00 00 00 00 00 00 Class: ELF64 Data: 2's complement, little endian Version: 1 (current) OS/ABI: Novell - Modesto ABI Version: 0 Type: EXEC (Executable file) Machine: Motorola Coldfire Version: ... | |
| | | | |
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. | |
| | | | |
blog.nuculabs.de
|
|
| | | | | I've recently finished reading a book called Practical Binary Analysis which I consider a state of the art book (review will come soon) and I would like to post my solution to the crackme found in chapter 5. 1. A New CTF ChallengeComplete the new CTF challenge unlocked by the oracle program!You can complete the entire challenge using only the tools discussedin this chapter and what you learned in Chapter 2. After completingthe challenge, don't forget to give the flag you found to the oracle tounlock the next challenge | |
| | | | |
www.humprog.org
|
|
| | | [AI summary] This blog post discusses the creation of custom program headers in ELF files to embed one ELF object inside another, enabling the inner object to be loadable when the outer object runs. The author outlines a method using a modified linker script, m4 processing, and a C program to adjust file offsets. The post also touches on broader implications for system design and user-space prototyping of Unix extensions. | ||
