commit 3b862722c60af9564e63382dfaf20ebbcb005237
parent e85e85158a61c21aba0810830b127e7136e0764c
Author: pyratebeard <root@pyratebeard.net>
Date: Sat, 16 Dec 2023 21:44:41 +0000
respect_my_authoritah
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/entry/respect_my_authoritah.md b/entry/respect_my_authoritah.md
@@ -2,7 +2,7 @@ I enjoy trying to improve security in the environments I manage as a sysadmin.
Recently I had been asked to improve the SSH security in an environment. SSH keys weren't really being used, so that was my first suggestion, but I needed to make key management as simple as possible without forgoing any security benefits; so I decided to take a proper look at [SSH Certificate Authorities](TK){target="_blank" rel="noreferrer"} (CA).
-I've known about SSH CA for a while, though never played around with it. Before taking it to into a production environment I decided to become familiar on my own turf.
+I've known about SSH CA for a while, though never played around with it. Before taking it into a production environment I decided to become familiar on my own turf.
There are two types of SSH CA, Host and User.
