cdransf/coryd.dev-eleventy
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

posts directory

Browse source
This commit is contained in:
Cory Dransfeldt 2023-03-11 20:22:08 -08:00
parent 9e00d9c09e
commit 5c6deac7a2
No known key found for this signature in database
24 changed files with 0 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
src/posts/data/ssh-directory-permissions.md Normal file
View file

@ -0,0 +1,22 @@
---
title: .ssh directory permissions
date: '2020-11-09'
draft: false
tags: ['ssh', 'development']
summary: I was recently setting up a new, always-on machine that I do occasional dev work. This dev work typically consists of routine maintenance and, a requirement of that, is sshing into and running software updates on manually managed servers (yes, manually managed).
---
I was recently setting up a new, always-on machine that I do occasional dev work. This dev work typically consists of routine maintenance and, a requirement of that, is sshing into and running software updates on manually managed servers (yes, manually managed[^1]).<!-- excerpt -->
I sync my `.ssh` configuration using [mackup](https://github.com/lra/mackup). However, while setting up and then using a key I received a warning that my configured `.ssh` directory permissions were too open. If you ever run into this, the solution is fairly simple[^2]:
```bash
chmod 700 ~/.ssh
chmod 644 ~/.ssh/id_rsa.pub
chmod 600 ~/.ssh/id_rsa
```
Try reconnecting using the key in question and the warning should be resolved.
[^1]: Think small-scale WordPress or one-off projects.
[^2]: Where `id_rsa` is your key name.