Q: What does the `/etc/shadow` file contain, and why is it separated from `/etc/passwd`?
/etc/passwd contains user account information (username, UID, GID, home directory, shell) and historically stored password hashes. However, /etc/passwd must be world-readable because many programs need to map UIDs to usernames.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Linux authentication files, password security.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
/etc/passwd contains user account information (username, UID, GID, home directory, shell) and historically stored password hashes. However, /etc/passwd must be world-readable because many programs need to map UIDs to usernames.
- Username
- Hashed password (using algorithms like SHA-512, prefixed with
$6$) - Date of last password change (in days since epoch)
- Minimum days between password changes
Remediation & Permanent Safeguards
/etc/shadow was introduced to separate the sensitive password hashes into a file that is readable only by root (permissions 640 or 600). This prevents unprivileged users from reading hashed passwords and attempting offline brute-force attacks. Each line in /etc/shadow contains: To check password aging for a user: chage -l username. To force a password change on next login: chage -d 0 username.
- Maximum password age
- Warning period before expiry
- Account expiration date
- Username
- Hashed password (using algorithms like SHA-512, prefixed with $6$)
- Date of last password change (in days since epoch)
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring /etc/shadow file contain SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring /etc/shadow file contain
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring /etc/shadow file contain Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring /etc/shadow file contain
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).