From 5be6a64ec835c49d0bf77434406c25eb8ecb4ecd Mon Sep 17 00:00:00 2001
From: friendly-rabbit-35
 <169707731+friendly-rabbit-35@users.noreply.github.com>
Date: Mon, 10 Jun 2024 10:32:55 -0700
Subject: [PATCH] Update directory paths of snap images and test side by side
 images

Signed-off-by: friendly-rabbit-35 <169707731+friendly-rabbit-35@users.noreply.github.com>
---
 content/posts/linux/Desktop Linux Hardening/index.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/content/posts/linux/Desktop Linux Hardening/index.md b/content/posts/linux/Desktop Linux Hardening/index.md
index 13bf660..6e6ceaf 100644
--- a/content/posts/linux/Desktop Linux Hardening/index.md	
+++ b/content/posts/linux/Desktop Linux Hardening/index.md	
@@ -144,8 +144,7 @@ Snap permissions can be managed via the Snap Store or Ubuntu's custom patched GN
 
 On Ubuntu, you can replace various .deb packages with strictly confined snaps to minimize the attack surface. Some examples of these packages are the printing stack or `ufw`:
 
-![Cups Snap](/images/ubuntu-cups-snap.png)
-![UFW Snap](/images/ubuntu-ufw-snap.png)
+![Cups Snap](ubuntu-cups-snap.png)![UFW Snap](ubuntu-ufw-snap.png)
 
 One caveat with Snap packages is that you only have control over the interfaces declared in their manifests. For example, Snap has separate interfaces for `audio-playback` and `audio-record`, but some packages will only declare the legacy `pulseaudio` interface which grants access to both play and record audio. Likewise, some applications may work perfectly fine with Wayland, but the package maintainer may only declare the X11 interface in their manifest. For these cases, you need to reach out to the maintainer of the snap to update the manifest accordingly.