A municipal low-privilege Linux user can read another user's private SSH keys due to weak home-directory permissions. What is the primary risk?
Select an answer to reveal the explanation.
Short Explanation
If you can read someone else's SSH private key, you can often walk through their front door on the next host. Loose home-directory permissions turn neighbor accounts into stepping stones. Fix the perms; do not shrug it off as wallpaper settings.
Full Explanation
SSH private keys authenticate as the key owner when passphrase and server policy allow. Weak home or .ssh directory permissions that expose those keys enable horizontal privilege movement between users and often onward to other systems. The issue is authentication material exposure, not cosmetics, and it does not prove SELinux is enforcing. Remediation centers on correct ownership, 700/600-class permissions, and key rotation where exposure occurred.