| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 1 | # D-Bus Mojo Connection Service |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | D-Bus Mojo Connection Service in Chrome is a D-Bus service that helps to |
| 6 | bootstrap CrOS services' Mojo connection. |
| 7 | |
| 8 | ## Bootstrap a new CrOS service |
| 9 | |
| Yeunjoo Choi | ba67727 | 2021-06-15 06:34:04 | [diff] [blame] | 10 | D-Bus Mojo Connection Service lives in [//chrome/browser/ash/dbus/mojo_connection_service_provider.h](https://chromium.googlesource.com/chromium/src.git/+/main/chrome/browser/ash/dbus/mojo_connection_service_provider.h). |
| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 11 | |
| 12 | Follow the example of CrOS Sensors' [changelist](https://chromium-review.googlesource.com/c/chromium/src/+/2352298). |
| 13 | |
| 14 | ### Steps to Add a usage for a CrOS process with a new D-Bus method: |
| Harvey Yang | 8e23bb1b | 2021-03-09 07:37:50 | [diff] [blame] | 15 | 1. Add a method name in both CrOS platform and Chrome. |
| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 16 | (Recommend: `platform2/system_api`) |
| 17 | 2. Add the busconfig policy in [MojoConnectionService.conf]. |
| 18 | 3. Upon a D-Bus request coming from the CrOS service, pass one endpoint of the |
| 19 | generated Mojo pipe to the component in Chrome that needs a Mojo channel to |
| Yeunjoo Choi | ba67727 | 2021-06-15 06:34:04 | [diff] [blame] | 20 | the CrOS service. Ex: [RegisterServer](https://chromium-review.googlesource.com/c/chromium/src/+/2352298/16/chrome/browser/ash/dbus/mojo_connection_service_provider.cc#74) in CrOS Sensors' usage. |
| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 21 | 4. Respond to the D-Bus request with the other endpoint of the generated Mojo |
| Yeunjoo Choi | ba67727 | 2021-06-15 06:34:04 | [diff] [blame] | 22 | pipe. (Recommend: use the helper function [SendResponse](https://chromium-review.googlesource.com/c/chromium/src/+/2352298/16/chrome/browser/ash/dbus/mojo_connection_service_provider.h#75)) |
| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 23 | |
| 24 | The Mojo pipe can also be generated in the CrOS process, and pass the endpoint |
| 25 | of it as the D-Bus argument to the service provider, instead of allowing Chrome |
| 26 | to generate the pipe. |
| 27 | |
| 28 | ### Steps to Add a usage for a CrOS process with an existing D-Bus method: |
| 29 | 1. Add the busconfig policy in [MojoConnectionService.conf]. |
| 30 | |
| Harvey Yang | 8e23bb1b | 2021-03-09 07:37:50 | [diff] [blame] | 31 | And that’s it. The method name and the logic in the service provider can be |
| 32 | reused. |
| Harvey Yang | 01729de | 2021-03-01 11:02:24 | [diff] [blame] | 33 | |
| 34 | ## Security |
| 35 | |
| 36 | UID filtering should be used to ensure only the needed processes are calling |
| 37 | the specific D-Bus methods, as processes/applications calling D-Bus APIs are |
| 38 | trusted (written and reviewed by Chromium/CrOS teams) and should have a |
| 39 | well-known UID to be filtered. |
| 40 | |
| 41 | UID filtering: Define access permission for each UID in |
| 42 | [MojoConnectionService.conf]. Only the processes run under the specific UIDs can |
| 43 | send respective D-Bus requests to the service provider. |
| 44 | |
| 45 | Arguments/tokens in D-Bus methods are still available if needed, which should |
| 46 | be enough for multi-login situations and handling failures. The arguments can |
| 47 | also be used to determine if Chromium should accept the request, and which Mojo |
| 48 | interface should be used to establish the Mojo channel. |
| 49 | |
| Yeunjoo Choi | ba67727 | 2021-06-15 06:34:04 | [diff] [blame] | 50 | [MojoConnectionService.conf]: https://chromium.googlesource.com/chromium/src.git/+/main/chrome/browser/ash/dbus/org.chromium.MojoConnectionService.conf |
