finished post, moved images but did so in wrong branch XD

content/posts/securing-ssh.md

@@ -26,7 +26,7 @@ gain access. With further configuration of SSH we can make the service
 a lot more secure.
 
 # **Configure SSH**
-![this is fine](/img/gifs/this-is-fine.gif)
+![this is fine](/gif/this-is-fine.gif)
 > **Famous last words:** Configuring SSH like many things in Linux is
 as simple as editing a few config files
 
@@ -123,7 +123,7 @@ sudo vim /etc/ssh/sshd_config
 For a new user this might be daunting. Take your time and you will be
 fine 😊
 
-![that's a big one](/img/gifs/thats-a-big-one.gif)
+![that's a big one](/gif/thats-a-big-one.gif)
 
 **Lines we want to modify**
 
@@ -268,7 +268,7 @@ Subsystem       sftp    /usr/lib/openssh/sftp-server
 #       PermitTTY no
 #       ForceCommand cvs server
 ```
-![not so bad](/img/gifs/star-trek-not-so-bad.gif)
+![not so bad](/gif/wasnt-so-bad.gif)
 
 **Now lets explain what we just did**
 * **Protocol 2** - released in 2006, SSH2 introduced improved
@@ -302,7 +302,7 @@ roll back the changes and troubleshoot.
 
 # **Success**
 
-![clap](/img/gifs/clap.gif)
+![clap](/gif/clap.gif)
 
 # **Setting up** ***Fail2Ban***
 _Fail2Ban_ is an intrusion prevention tool. Although we are slowing
@@ -394,7 +394,7 @@ refused.
 ssh test@host -p 2222
 ```
 _Fail2Ban_ should do something along the lines of ...
-![you shall not pass](/img/gifs/you-shall-not-pass.gif)
+![you shall not pass](/gif/you-shall-not-pass.gif)
 log back in as your  normal user, remove the test user and restore the
 sshd config.
 
@@ -422,4 +422,4 @@ a remote host, re-configure the sshd config to lockdown authentication
 and last but not least install and configure Fail2Ban to block pesky
 attackers.
 
-![proud](/img/gifs/proud.gif)
+![proud](/gif/proud.gif)