NEWPractise supported commands in browser simulations, alongside the lesson.Try a browser practice exercise.Try a lab♥ Codelivly is 100% free, no paywall. If it helped you, chip in to keep it running.100% free. Help keep it so.Support us
Network Services Administration
This comprehensive learning path bridges the gap between foundational networking and enterprise infrastructure security.
ViewNetwork Security and Hardening
This comprehensive learning path dives deep into the principles and practices of securing network infrastructure. You wi
ViewPreview · 30 min
Understand how Linux tracks files using inodes. Learn the difference between hard links and symbolic links, and discover how attackers abuse symlinks in world-writable directories to execute devastating privilege escalation attacks.
To the kernel, a file name is only a label. Every file is really an inode (index node): a numbered record with the file's details. Knowing this explains how links work — and one classic privilege-escalation trick, the symlink attack.
When a file is created, the filesystem stores two things: the data blocks (the content) and the inode (the metadata). The inode holds:
The inode does not contain the file name. The name lives in the directory, as a label that points to the inode number. See the number with ls -i, and all metadata with stat.
Create a free account to unlock the rest of this task, complete tasks, and earn Rep.
Sign in