PrivSec-dev/privsec.dev
1
0
Fork 0
mirror of https://github.com/PrivSec-dev/privsec.dev synced 2025-02-20 18:31:35 -05:00
Code

Update directory paths of snap images and test side by side images

Browse Source 
Signed-off-by: friendly-rabbit-35 <169707731+friendly-rabbit-35@users.noreply.github.com>
This commit is contained in:
friendly-rabbit-35 2024-06-10 10:32:55 -07:00 committed by GitHub
parent 3e3ee1f3cc
commit 5be6a64ec8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/posts/linux/Desktop Linux Hardening/index.md
View File

@ -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.