Run chmod 700 ~/.ssh.
chmod 700 ~/.ssh
Mission 69
Directory modes
Review why private directories use tighter modes.
Permissions and userschmodstatls
Lesson 69 of 360
0/360 lessons
0/17 missions
Permissions and users · 7 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
7 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run stat ~/.ssh.
stat ~/.ssh
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.
Inspect and set a private directory mode.
Use chmod 700 ~/.ssh.
Sensitive config folders should not be casually readable.
- Only checking files, not their parent folders.
- Using file-mode intuition for directories.
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.