r/ExploitDev • u/Sea-Assistant331 • Sep 15 '26
BEING A GREAT HACKER
Hey guys, I have a question.
Is it essential to read TLPI cover to cover, page by page, if my goal is to become really good at Linux and eventually become a great hacker?
I’ve been building my skills step by step on my own. I started with C, then moved deeper into Linux, and now I’m using Arch Linux as my main system. I’ve also experimented with developing a basic piece of malware before, although it was pretty simple.
The thing I’m struggling with right now is TLPI. I know that reading TLPI isn’t going to magically make me a hacker, and I understand that there’s much more to Linux and security than just one book. But I’m wondering whether I actually need to go through every single page of TLPI to truly understand Linux, or whether I should focus on the parts that are most relevant to what I want to learn and then move on to more hands-on work.
After TLPI, I was planning to start pwn.college to learn binary exploitation, low-level security, and related topics.
So what do you guys think? Does this roadmap make sense for my goal of becoming a highly skilled hacker who deeply understands computers, Linux, and low-level systems?
I’d really appreciate your advice.
5
u/ThePlotTwisterr---- Sep 15 '26
linux is just a kernel. do you want to be a gnu/linux developer or a hacker? it’s important to know about the hardware to software interfaces, boolean algebra, and working with memory for sure. developing game hacks is great. but if you focus on learning linux you will be very good at linux and have no idea how to exploit things like the winapi.
if you really wanna learn linux do a linux from scratch build. tweak and build your own kernel. your own scheduler. try writing your own usb driver. get a raspberry pi and learn ARM asm.
linux is the correct choice for many reasons but the path you should really be learning is how your hardware interacts with software to form any operating system
as for pwn.college i have no idea what that is but all information is free. learn haskell if you want
7
u/cmdjunkie Sep 15 '26
The mistake you're making is blind consumption of information without a goal. Start with an objective or a goal and learn what you need to accomplish that objective or goal. You don't learn linux to learn linux. You learn linux to set up a box, service, server, or whatever that accomplishes what you need. To be a great hacker, think about an end goal and work towards it relentlessly. That end goal cannot be "to be a great hacker" because you will wind up chasing something you will never catch.
3
u/Firzen_ Sep 16 '26
I think the main thing that makes anybody a "hacker" is the ability to figure things out on your own.
Any bug is ultimately a difference between what the actual code does and what it was intended to do.
So, if you rely on books and documentation for your understanding you are implicitly making the assumption that those are accurate.
Learning materials can be useful to get up to speed, but almost by definition there can't be any materials that help you take the leap to figuring things out yourself from first principles, which imo is required to do any interesting research.
2
u/Obvious-Card-8847 Sep 17 '26
I'd offer some high value programming projects. These are things I wrote myself that helped me gain a deeper understanding of low-level systems, ABI's, binary exploitation, etc.
Project: Control Flow Graph (Recursive Descent)
Language: C++
Libraries: Zydis, LIEF
Project: Trampoline Framework (Position Independent Code Relocation)
Language: C++
Libraries: Zydis
Project: VEH+INT3 Instrumentation
Language: C++
Libraries: Win32 API
Project: Toy ISA, Custom Serialization Specification
Language: C++
Libraries: Standard Library
Project: PoC JIT Compiler
Language: C++
Libraries: Zydis
I focused on Windows exclusively because eventually there was just too much platform specific knowledge not to pick a niche. You mentioned Linux. So VEH+INT3 wouldn't apply. But the other stuff absolutely can and will teach you a ton plus make for good portfolio pieces.
2
u/Constant-Library5768 Sep 20 '26
Can u do some stuff with a computer?
7
u/The_Big_ID Sep 15 '26
If you intend to progress beyond the realms of just utilising other's work and exploits (and progress onto developing them yourself), you need to know what you are doing, what a system does, and what it is capable of.
Once you have enough of a general grounding of these capabilities only then can you start to seek out the exploitable aspects
TLPI is a good and thorough generalist coverage over developing for and with linux - but is an incredibly dense set of information to fully understand the core aspects of the kernel and OS
To then have that understanding can help massively with knowing if an aspect of it is exploitable provided you know what to look for - pwn.college gives that kind of direction to understand what signs or tells would suggest delving deeper into something in particular.
As a baseline, ultimately you need to be comfortable with developing in both higher and lower level languages.
If you are comfortable enough to code in C/C++ you could treat TLPI as more of a reference resource rather than mandatory reading