hmcclungiii · July 13, 2021 00:12 · Nov 4, 2015
diff --git a/Fixing UNPROTECTED PRIVATE KEY FILE.md b/Fixing UNPROTECTED PRIVATE KEY FILE.md
@@ -0,0 +1,43 @@
+#Fixing “WARNING: UNPROTECTED PRIVATE KEY FILE!” on Linux
+
+If you are getting this error then you probably reset the permissions on your hidden .ssh directory in your user folder, and your keys aren’t going to work anymore. It’s very important that these files not be writable by just anybody with a login to the box, so openssh will give you an error if you try to use them.
+
+The full error message:
+
+```sh
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+Permissions 0744 for '/home/geek/.ssh/id_rsa' are too open.
+It is recommended that your private key files are NOT accessible by others.
+This private key will be ignored.
+bad permissions: ignore key: /home/geek/.ssh/id_rsa
+```
+
+To fix this, you’ll need to reset the permissions back to default:
+
+```sh
+sudo chmod 600 ~/.ssh/id_rsa
+sudo chmod 600 ~/.ssh/id_rsa.pub
+```
+
+If you are getting another error:
+
+```sh
+Are you sure you want to continue connecting (yes/no)? yes
+Failed to add the host to the list of known hosts (/home/geek/.ssh/known_hosts).
+```
+
+This means that the permissions on that file are also set incorrectly, and can be adjusted with this:
+
+```sh
+sudo chmod 644 ~/.ssh/known_hosts
+```
+
+Finally, you may need to adjust the directory permissions as well:
+
+```sh
+sudo chmod 755 ~/.ssh
+```
+
+This should get you back up and running.