Remove FreeBSD specific security config

Since we're going to require clients to have been spawned by sway to be
trusted, we can ditch the FreeBSD config

2 files changed, 6 insertions, 34 deletions

diff --git a/meson.build b/meson.build
index 96d74bd3..f8303dd5 100644
--- a/meson.build
+++ b/meson.build
@@ -168,21 +168,12 @@ configure_file(
         install_dir: sysconfdir + '/sway'
 )
 
-if is_freebsd
-        configure_file(
-                configuration: config,
-                input: 'security.d/10-freebsd.in',
-                output: '@BASENAME@',
-                install_dir: sysconfdir + '/sway/security.d'
-        )
-else
-        configure_file(
-                configuration: config,
-                input: 'security.d/00-defaults.in',
-                output: '@BASENAME@',
-                install_dir: sysconfdir + '/sway/security.d'
-        )
-endif
+configure_file(
+        configuration: config,
+        input: 'security.d/00-defaults.in',
+        output: '@BASENAME@',
+        install_dir: sysconfdir + '/sway/security.d'
+)
 
 install_data(
         'sway.desktop',
diff --git a/security.d/10-freebsd.in b/security.d/10-freebsd.in
deleted file mode 100644
index 533b526a..00000000
--- a/security.d/10-freebsd.in
+++ /dev/null
@@ -1,19 +0,0 @@
-# sway security rules
-#
-# FreeBSD does not support getting client PID from server side
-# so we can not know the path to the client's binary.
-#
-# The solution for now is to be permissive and allow all
-# features by default for any client.
-
-# Configures enabled compositor features for specific programs
-permit * fullscreen keyboard mouse background screenshot panel lock 
-
-ipc * {
-   * enabled
-   events {
-     * enabled
-   }
-}
-
-