moved all images to webm

content/posts/securing-ssh.md

@@ -26,7 +26,8 @@ gain access. With further configuration of SSH we can make the service
 a lot more secure.
 
 # **Configure SSH**
-![this is fine](/gif/this-is-fine.gif)
+{{< video label="this is fine" webm="/webm/this-is-fine.webm" >}}
+
 > **Famous last words:** Configuring SSH like many things in Linux is
 as simple as editing a few config files
 
@@ -123,7 +124,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](/gif/thats-a-big-one.gif)
+{{< video label="thats a big one" webm="/webm/thats-a-big-one.webm" >}}
 
 **Lines we want to modify**
 
@@ -268,7 +269,8 @@ Subsystem       sftp    /usr/lib/openssh/sftp-server
 #       PermitTTY no
 #       ForceCommand cvs server
 ```
-![not so bad](/gif/wasnt-so-bad.gif)
+
+{{< video label="not so bad" webm="/webm/wasnt-so-bad.webm" >}}
 
 **Now lets explain what we just did**
 * **Protocol 2** - released in 2006, SSH2 introduced improved
@@ -302,7 +304,7 @@ roll back the changes and troubleshoot.
 
 # **Success**
 
-![clap](/gif/clap.gif)
+{{< video label="clap" webm="/webm/clap.webm" >}}
 
 # **Setting up** ***Fail2Ban***
 _Fail2Ban_ is an intrusion prevention tool. Although we are slowing
@@ -394,7 +396,8 @@ refused.
 ssh test@host -p 2222
 ```
 _Fail2Ban_ should do something along the lines of ...
-![you shall not pass](/gif/you-shall-not-pass.gif)
+{{< video label="you shall not pass" webm="/webm/you-shall-not-pass.webm" >}}
+
 log back in as your  normal user, remove the test user and restore the
 sshd config.
 
@@ -422,4 +425,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](/gif/proud.gif)
+{{< video label="proud" webm="/webm/proud.webm" >}}