Added [in-progress] Developer Guides

[AGL/documentation.git] / docs / 2_Architecture_Guides / 2.2_Security_Blueprint / 7_Connectivity / 1.2.7.1_Bus_And_Connectors.md

diff --git a/docs/2_Architecture_Guides/2.2_Security_Blueprint/7_Connectivity/1.2.7.1_Bus_And_Connectors.md b/docs/2_Architecture_Guides/2.2_Security_Blueprint/7_Connectivity/1.2.7.1_Bus_And_Connectors.md
index 4403d41..c7b577a 100644 (file)
--- a/docs/2_Architecture_Guides/2.2_Security_Blueprint/7_Connectivity/1.2.7.1_Bus_And_Connectors.md
+++ b/docs/2_Architecture_Guides/2.2_Security_Blueprint/7_Connectivity/1.2.7.1_Bus_And_Connectors.md
@@ -1,12 +1,7 @@
 ---
-edit_link: ''
 title: Bus and connectors
-origin_url: >-
-  https://raw.githubusercontent.com/automotive-grade-linux/docs-sources/master/docs/security-blueprint/part-7/1-BusAndConnectors.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 -->
-
 # Bus
 
 We only speak about the **CAN** bus to take an example, because the different
@@ -15,8 +10,8 @@ engineering and the main argument to improve their security is to encrypt data
 packets. We just describe them a bit:
 
 - **CAN**: Controller Area Network, developed in the early 1980s, is an
-  event-triggered controller network for serial communication with data rates
-  up to one MBit/s. **CAN** messages are classified over their respective
+  event-triggered controller network for serial communication with data rates up
+  to one MBit/s. **CAN** messages are classified over their respective
   identifier. **CAN** controller broadcast their messages to all connected nodes
   and all receiving nodes decide independently if they process the message.
 - **FlewRay**: Is a deterministic and error-tolerant high-speed bus. With a data
@@ -37,16 +32,17 @@ packets. We just describe them a bit:
 On just about every vehicle, **ECU**s (**E**lectronic **C**ontrol **U**nits)
 communicate over a CAN bus, which is a two-wire bus using hardware arbitration
 for messages sent on the shared medium. This is essentially a *trusted* network
-where all traffic is visible to all controllers and any controller can send any message.
+where all traffic is visible to all controllers and any controller can send any
+message.
 
 A malicious **ECU** on the CAN bus can easily inject messages destined for any
 other device, including things like the instrument cluster and the head unit.
-There are common ways for hardware to do USB to CAN and open source software to send
-and receive messages. For example, there is a driver included in the Linux kernel
-that can be used to send/receive CAN signals. A malicious device on the CAN bus can
-cause a great number of harmful things to happen to the system, including: sending
-bogus information to other devices, sending unintended commands to ECUs,
-causing DOS (Denial Of Service) on the CAN bus, etc.
+There are common ways for hardware to do USB to CAN and open source software to
+send and receive messages. For example, there is a driver included in the Linux
+kernel that can be used to send/receive CAN signals. A malicious device on the
+CAN bus can cause a great number of harmful things to happen to the system,
+including: sending bogus information to other devices, sending unintended
+commands to ECUs, causing DOS (Denial Of Service) on the CAN bus, etc.
 
 <!-- section-config -->
 
@@ -56,7 +52,9 @@ Connectivity-BusAndConnector-Bus-1 | CAN       | Implement hardware solution in
 
 <!-- end-section-config -->
 
-See [Security in Automotive Bus Systems](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.92.728&rep=rep1&type=pdf) for more information.
+See [Security in Automotive Bus
+Systems](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.92.728&rep=rep1&type=pdf)
+for more information.
 
 # Connectors