From 52d5795d04a3078d87f10414a328c48e4446957f Mon Sep 17 00:00:00 2001
From: Hugo <hugo@whynothugo.nl>
Date: Sat, 28 Jan 2023 14:13:37 +0100
Subject: [PATCH] Running SUID is not longer supported

---
 Running-Sway-without-systemd.md | 20 +-------------------
 1 file changed, 1 insertion(+), 19 deletions(-)

diff --git a/Running-Sway-without-systemd.md b/Running-Sway-without-systemd.md
index 034d4c4..ad43765 100644
--- a/Running-Sway-without-systemd.md
+++ b/Running-Sway-without-systemd.md
@@ -49,22 +49,4 @@ To have sway run as root in order to gain access to the resources you need, you
 chmod +s /usr/bin/sway
 ```
 
-Sway will fork into a minimal slave process to keep these privileges, while dropping its own. As with any program, using setuid has serious security implications.
-
-# Tips and Tricks
-
-## Archlinux without systemd/elogind
-In order to automatically keep the extra privileges after a sway installation/upgrade, add the following pacman hook to `/etc/pacman.d/hooks`:
-```
-[Trigger]
-Operation = Install
-Operation = Upgrade
-Type = Package
-Target = sway
-Target = sway-git
-
-[Action]
-Description = Applying setuid-bit to sway
-When = PostTransaction
-Exec = /usr/bin/chmod +s /usr/bin/sway
-```
\ No newline at end of file
+Sway will fork into a minimal slave process to keep these privileges, while dropping its own. As with any program, using setuid has serious security implications.
\ No newline at end of file