jens/flipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Docs corrections in establishing-a-connection (#220)

Browse Source 
Summary:
The title gets taken from the header, so is duplicated.
Pull Request resolved: https://github.com/facebook/flipper/pull/220

Reviewed By: passy

Differential Revision: D9244730

Pulled By: jknoxville

fbshipit-source-id: d4701cb4af6f551a35cfa02c9ff43aef495f1da0
This commit is contained in:
John Knox
2018-08-13 03:53:03 -07:00
committed by Facebook Github Bot
parent 89c89e219c
commit ed67ce527d
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/establishing-a-connection.md
View File

@@ -4,8 +4,6 @@ title: Establishing a connection
sidebar_label: Establishing a connection
---
# Establishing a Connection
Below is an outline of how a connection is established between an app with with our SDK integrated, and the desktop app. This all goes on behind the scenes inside the mobile SDK, so users shouldn't need to worry about it.
## Transport Protocol
@@ -20,7 +18,7 @@ Any mobile app with the Flipper SDK installed will continually attempt to connec
## Certificate Exchange
To avoid mobile apps from connecting to untrusted ports on localhost, they will only connect to servers that have a valid, trusted TLS certificate.
In order for the mobile app to know which certificates it can trust, it conducts a certificate exchange with the desktop app before making it can make its first secure connection.
In order for the mobile app to know which certificates it can trust, it conducts a certificate exchange with the desktop app before it can make its first secure connection.
This is achieved through the following steps:
* Desktop app starts an insecure server on port 8089.