Added [in-progress] Developer Guides
[AGL/documentation.git] / docs / 2_Architecture_Guides / 2.2_Security_Blueprint / 5_Platform / 1.2.5.3_SystemBus.md
index 0e37e20..71a2212 100644 (file)
@@ -1,12 +1,7 @@
 ---
-edit_link: ''
 title: SystemBus
-origin_url: >-
-  https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-5/3-SystemBus.md
 ---
 
-<!-- WARNING: This file is generated by fetch_docs.js using /home/boron/Documents/AGL/docs-webtemplate/site/_data/tocs/architecture/master/security_blueprint-security-blueprint-book.yml -->
-
 # D-Bus
 
 D-Bus is a well-known **IPC** (Inter-Process Communication) protocol (and
@@ -14,12 +9,14 @@ 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
+`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.