Skip to content

Commit

Permalink
[fix] no syntatic sugar for alert includes :(
Browse files Browse the repository at this point in the history
  • Loading branch information
EsseLowNitro authored Dec 20, 2024
1 parent 817559b commit 5a07c8d
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 15 deletions.
10 changes: 4 additions & 6 deletions _includes/alert.html
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
{% assign text = include.content | split: '' %}
{% assign text = include.content | split: '<br>' %}

<div class="alert {{ include.type }}">
<p>
Expand All @@ -19,11 +19,9 @@
{{ include.type | capitalize }}
</em>
{% for line in text %}
{% if line != '' %}
<p>
{{ line }}
</p>
{% endif %}
<p>
{{ line }}
</p>
{% endfor %}
</p>
</div>
8 changes: 2 additions & 6 deletions content/IMAGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,7 @@ Table of Contents

{% include alert.html type='note' content='This is a relative recommendation between the desktop environments available on secureblue. GNOME has some extra security niceties like the ones listed below. It however does not solve any of the fundamental issues with desktop linux security.' %}

{% include alert.html type='caution' content='Silverblue utilizes GNOME, which is the only desktop that secures privileged wayland protocols like screencopy. This means that on non-GNOME systems, applications can access screen content of the entire desktop. This implicitly includes the content of other applications. It\'s primarily for this reason that GNOME images are recommended. KDE has <a href="https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/7">plans</a> to fix this.

GNOME also provides <a href="https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/213">thumbnailer sandboxing</a> in Gnome Files, which mitigates attacks <a href="https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-compromising-linux-desktop.html">via thumbnailers</a>.' %}
{% include alert.html type='caution' content='Silverblue utilizes GNOME, which is the only desktop that secures privileged wayland protocols like screencopy. This means that on non-GNOME systems, applications can access screen content of the entire desktop. This implicitly includes the content of other applications. It\'s primarily for this reason that GNOME images are recommended. KDE has <a href="https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/7">plans</a> to fix this.<br>GNOME also provides <a href="https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/213">thumbnailer sandboxing</a> in Gnome Files, which mitigates attacks <a href="https://scarybeastsecurity.blogspot.com/2016/11/0day-exploit-compromising-linux-desktop.html">via thumbnailers</a>.' %}

### Stable

Expand Down Expand Up @@ -112,9 +110,7 @@ GNOME also provides <a href="https://gitlab.gnome.org/GNOME/gnome-desktop/-/issu

## Server

{% include alert.html type='note' content='
After you finish setting up your <a href="https://fedoraproject.org/coreos/">Fedora CoreOS</a> installation, you will need to disable `zincati.service` before rebasing to securecore.
' %}
{% include alert.html type='note' content='After you finish setting up your <a href="https://fedoraproject.org/coreos/">Fedora CoreOS</a> installation, you will need to disable `zincati.service` before rebasing to securecore.' %}

| Name | Base | Nvidia Support | ZFS Support |
|-------------------------------------------|-----------|-------------------------|-------------|
Expand Down
4 changes: 1 addition & 3 deletions content/INSTALL.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,7 @@ The following is advice on what to do before and during the installation of a Fe

{% include alert.html type='note' content='The cross-platform Fedora Media Writer is the <em>official, tested and supported</em> method for the creation of bootable media. Instructions (alongside a word on alternative methods) are available <a href="https://docs.fedoraproject.org/en-US/fedora/latest/preparing-boot-media/">here</a>.' %}

{% include alert.html type='tip' content='If you don\'t already have a Fedora Atomic installation, use a Fedora Atomic ISO that matches your secureblue target image to install one. If you want to use a secureblue Silverblue image, start with the Fedora Silverblue ISO, Kinoite for Kinoite, Sericea (Sway Atomic) for Sericea and all the Wayblue images, and CoreOS for all the securecore images.

For more details on the available images, have a look at the <a href="/images">list of available images</a> before proceeding.' %}
{% include alert.html type='tip' content='If you don\'t already have a Fedora Atomic installation, use a Fedora Atomic ISO that matches your secureblue target image to install one. If you want to use a secureblue Silverblue image, start with the Fedora Silverblue ISO, Kinoite for Kinoite, Sericea (Sway Atomic) for Sericea and all the Wayblue images, and CoreOS for all the securecore images.<br>For more details on the available images, have a look at the <a href="/images">list of available images</a> before proceeding.' %}

{% include alert.html type='caution' content='The Fedora 41 ISO contains a bugged version of rpm-ostree. As such, after using it to install Fedora Atomic, you <em>must</em> run rpm-ostree upgrade and then restart, before running the secureblue installer.' %}

Expand Down

0 comments on commit 5a07c8d

Please sign in to comment.