summaryrefslogtreecommitdiffstats
path: root/security-blueprint/part-5/3-SystemBus.md
diff options
context:
space:
mode:
Diffstat (limited to 'security-blueprint/part-5/3-SystemBus.md')
-rw-r--r--security-blueprint/part-5/3-SystemBus.md24
1 files changed, 0 insertions, 24 deletions
diff --git a/security-blueprint/part-5/3-SystemBus.md b/security-blueprint/part-5/3-SystemBus.md
deleted file mode 100644
index e2af387..0000000
--- a/security-blueprint/part-5/3-SystemBus.md
+++ /dev/null
@@ -1,24 +0,0 @@
-# D-Bus
-
-D-Bus is a well-known **IPC** (Inter-Process Communication) protocol (and
-daemon) that helps applications to talk to each other. The use of D-Bus is great
-because it allows to implement discovery and signaling.
-
-The D-Bus session is by default addressed by environment variable
-`DBUS_SESSION_BUS_ADDRESS`. Using **systemd** variable `DBUS_SESSION_BUS_ADDRESS`
-is automatically set for user sessions. D-Bus usage is linked to permissions.
-
-D-Bus has already had several [security issues](https://www.cvedetails.com/vulnerability-list/vendor_id-13442/D-bus-Project.html)
-(mostly **DoS** issues), to allow applications to keep talking to each other.
-It is important to protect against this type of attack to keep the system more
-stable.
-
-
-<!-- section-config -->
-
-Domain | Object | Recommendations
---------------- | -------------- | ------------------------------------
-Platform-DBus-1 | Security model | Use D-Bus as IPC.
-Platform-DBus-2 | Security model | Apply D-BUS security patches: [D-Bus CVE](https://www.cvedetails.com/vulnerability-list/vendor_id-13442/D-bus-Project.html)
-
-<!-- end-section-config -->