Run chmod 600 ~/.ssh/authorized_keys.
chmod 600 ~/.ssh/authorized_keys
Lesson 68 of 360
0/360 lessons
0/17 missions
Permissions and users · 8 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
8 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run stat ~/.ssh/authorized_keys.
stat ~/.ssh/authorized_keys
Run ls -la ~/.ssh.
ls -la ~/.ssh
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Use chmod and stat on a sensitive file.
Try chmod 600 on authorized_keys.
SSH key files often require restrictive permissions.
- Making private files world-readable.
- Changing mode without checking ownership.
Reference
Commands in this lesson.
ls [-la] [path]
List lab files and folders.
chmod <mode> <path>
Change a simulated numeric permission mode.
stat <path>
Show lab file details.
lsof
Show simulated files and sockets opened by services.