conf/sway/config.d/autostart-communication.conf

@@ -1,6 +1,7 @@
 # Signal in wayland and tray
-# --start-in-tray - would be nice, but then I cannot open it from there, thus --use-tray-icon
-#exec --no-startup-id flatpak run org.signal.Signal --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations --use-tray-icon
+# --disable-gpu - https://github.com/signalapp/Signal-Desktop/issues/2567#issuecomment-457282578
+# --start-in-tray - would be nice, but then I cannot open it from there, trus --use-tray-icon
+#exec --no-startup-id flatpak run org.signal.Signal --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --ozone-platform=wayland --disable-gpu --use-tray-icon
 
 # Telegram
 exec --no-startup-id flatpak run --env=LC_ALL=en_US.utf8 org.telegram.desktop -startintray
@@ -16,11 +17,15 @@ exec --no-startup-id flatpak run im.dino.Dino --gapplication-service
 # Gajim nightly, also electronless XMPP
 #exec --no-startup-id flatpak run org.gajim.Gajim.Devel
 
-# Instant messenger as email client
-exec --no-startup-id flatpak run chat.delta.desktop --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations
+# Instant messenger as email client, no wayland support https://github.com/deltachat/deltachat-desktop/issues/2800
+# Wayland would be enabled by: --enable-features=UseOzonePlatform,WaylandWindowDecorations,WebRTCPipeWireCapturer --ozone-platform=wayland
+# Excluded from Mullvad to avoid Gandi.net blocklist resulting inability to send
+# mail
+#exec --no-startup-id /usr/bin/mullvad-exclude /var/lib/flatpak/exports/bin/chat.delta.desktop --disable-gpu $@
+#exec --no-startup-id /var/lib/flatpak/exports/bin/chat.delta.desktop --disable-gpu $@
 
 # Mattermost, I fear it's Electron.
-#exec --no-startup-id flatpak run com.mattermost.Desktop --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations
+#exec --no-startup-id flatpak run com.mattermost.Desktop
 
 # Lith, WeeChat Relay client. Sleeping so keyring has time to start first,
 # otherwise the NextCloud issue of starting too early on SSD happens

conf/sway/config.d/autostart-foot-nordvpn-info.conf

@@ -1,3 +1,2 @@
-exec --no-startup-id sleep 15 && foot --title=nordvpn nordvpn connect p2p
 exec --no-startup-id foot --title=nordvpnd\ log journalctl -u nordvpnd -f
 exec --no-startup-id foot --title=nordvpn\ status watch 'nordvpn status'

etc/ssh/sshd_config.d/00-basic-security.conf

@@ -1,6 +1,8 @@
-# Ed25519 is fine, but DSA is broken, time has passed RSA and ecdsa is sus…
+# RSA and Ed25519 are fine, but DSA is broken and ecdsa is suspicious
 # Missing keys?
 # ssh-keygen -t ed25519 -N "" -f /etc/ssh/ssh_host_ed25519_key
+# ssh-keygen -t rsa -N "" -f /etc/ssh/ssh_host_rsa_key
+HostKey /etc/ssh/ssh_host_rsa_key
 HostKey /etc/ssh/ssh_host_ed25519_key
 
 # Includes public keys in logins