Firefox OS/Remote Control: Difference between revisions

Firefox OS/Remote Control (view source)

Revision as of 09:32, 15 April 2016

778 bytes removed , 15 April 2016

Update architecture to fennec extension based implementation

Eric Tsai

133

edits

@@ Line 1: / Line 1: @@
 == Introduction ==
-Remote control is a new feature for Firefox OS on TV. We hope user can control TV at any device without installing any APP. Consider compatibility, remote control uses HTTP and AJAX as communication protocol between TV and user. User can easily connect to TV via open his/her browser, enter URL on TV and use the virtual touchpad to control TV just in seconds.
+Remote control is a feature for Firefox OS on TV. After [https://addons.mozilla.org/en-US/android/addon/send-tab-to-tv/ Send tab to TV], user can easily extend browsing experience on TV via Firefox on Android, using virtual touchpad to control TV.
 Meta Bug: {{Bug|1205939}}
@@ Line 17: / Line 17: @@
 * [[Firefox_OS/Remote_Control_Service|Remote Control Service]]: Entry point of remote control feature. Control service related logic and data in runtime.
-* HTTP Server: Serves connections from user. Two types files can be served:
+* TLS server: Serves connections from user.
-** Static file: Stored in Remote Control Client App, packaged in app://remote-control-client.gaiamobile.org
-** Service script: Handle AJAX request and response for secure connection initialization, PIN code pairing and control event processing. Packaged in resource://gre/res/remotecontrol.
-* Remote Control App: Provides service related user interface on TV. Communicate with Remote Control Service via MozSettings.
-User interaction of remote control is divided into three parts:
+User interaction of remote control is divided into two parts:
-# Establish secure connection
+# Peer authentication
-# PIN code pairing (optional, by user settings)
 # Control event processing
-=== Establish secure connection ===
+=== Peer authentication ===
-Remote control is designed to protect data transmitted between client and server, for example: user input string may contains privacy data. Consider user scenario for remote control is in local network, TV is not able to get a unique name to provide HTTPS; remote control uses proprietary protocol to establish secure connection. Client is forced to exchange symmetric key (AES-GCM) with server in the first time. After key exchange, server uses UUID in cookie to identify client and key to decrypt messages. Following describes how keys are exchanged:
+Remote control is designed to protect data transmitted between client and server, for example: user input string may contains privacy data. The connection is based on self-signed TLS server. To prevent man in the middle(MITM) attack, we adopt [https://en.wikipedia.org/wiki/Password_Authenticated_Key_Exchange_by_Juggling J-PAKE] to exchange symmetric key for peer authentication. Following describes how it works:
-[[File:RemoteControl SecureConnectionInitialization.png]]
+[[File:RemoteControl_FirstTimeHandshake.png]]
 # The user opens the URL in the client (e.g. mobile browser).