Borrowing Root Without Living There
One account can do anything, including anything wrong. The whole discipline of running a system safely is: stay ordinary, and borrow that power one command at a time.
Permissions and ownership decide what I can touch. Is there an account that ignores all of it?
There is: rootrootThe all-powerful administrator account on a Unix system, allowed to do absolutely anything — including irreversible damage., the superuser. It can do absolutely anything — which is exactly why the skill is not using it most of the time.
The account with no guard rails
root bypasses every permission check. That makes it necessary for real administration — installing software, editing system files — and dangerous for everything else. A mistake as an ordinary user hits one file you own. The same mistake as root can hit the whole machine, with nothing to stop it.
As wren: rm important.txt -> deletes one of your files. Bad, recoverable.
As root: rm -rf /etc -> deletes the system's configuration. Catastrophic.
As root: chmod 777 / -> opens the entire machine. Silent, immediate.
- Line 1An ordinary user is contained by permissions — the blast radius of a mistake is your own files.
- Line 2root has no such containment. The permission model that protects everyone else does not apply to it. Power and danger are the same thing here.
Borrow, do not live
The modern discipline is to stay an ordinary user and reach for root only when a task genuinely needs it, using sudosudo"Do this one command as the superuser" — a controlled, logged way to borrow administrator power for a single action rather than living with it.: "do this one command as the superuser". You get the power for a single action, it is logged, and then you are ordinary again. You never live as root.
# ordinary action: no sudo needed
$ ls /home/wren
# system action: install software, needs root for this one command
$ sudo apt install nmap
[sudo] password for wren:
# you authenticated once, for one command, and it was recorded
# then you are back to being a normal user. root was borrowed, not inhabited.
Why is sudo command considered safer than just logging in as root and staying there, even though both can do the same things?
Which is the safest habit?
Living as root
- A root shell open all day "to save time"
- Copy-pasting a sudo command from the internet without reading it
- Running everything elevated because one thing needed itBorrowing root
- An ordinary user by default; sudo only where genuinely required
- Reading any elevated command fully before you run it
- Treating each sudo as a small, deliberate, recorded decisionThe most trusted administrators use root the least. Power you reach for deliberately is safe; power you sit inside all day is an accident waiting for a tired moment.
So the goal is not to have power. It is to borrow it only when needed.
Precisely. Stay ordinary, elevate deliberately, read before you run. That discipline is what separates people who administer systems for years from people who wipe one in an afternoon.
And from my side, a machine where everyone lives as root is a machine where one mistake — theirs or one I induce — owns everything. Least privilege is as much your defence against yourself as against me.
Legal
Use sudo and root only on systems you own or are explicitly authorised to administer. Elevating privileges on a system you do not have permission for — even if you can — is the definition of an intrusion, not a lesson exercise.
So one account can do anything, and the discipline is to touch it as little as possible: stay an ordinary user, borrow root through sudosudo"Do this one command as the superuser" — a controlled, logged way to borrow administrator power for a single action rather than living with it. for single deliberate actions, and read before you run. With permissions and privilege understood, you have the security foundation the whole platform builds on — from here, the paid courses put it to work on real systems and real targets.