summaryrefslogtreecommitdiffstats
path: root/third_party/mach_override
diff options
context:
space:
mode:
authorjamiewalch@chromium.org <jamiewalch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-04 06:26:01 +0000
committerjamiewalch@chromium.org <jamiewalch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-04 06:26:01 +0000
commit8835692aa95097e2df4a2ec2b2db4768578b06a0 (patch)
tree3eb40c08525740259ff976b617befdacad442541 /third_party/mach_override
parentde1bb9caab81d7a80dac9ebe59a5ea2aa56048dd (diff)
downloadchromium_src-8835692aa95097e2df4a2ec2b2db4768578b06a0.zip
chromium_src-8835692aa95097e2df4a2ec2b2db4768578b06a0.tar.gz
chromium_src-8835692aa95097e2df4a2ec2b2db4768578b06a0.tar.bz2
This CL adds the "request pairing" implementation between the web-app and the host. Specifically:
* Adds a pairing registry to the Chromoting host. * Checks the state of the "remember me" checkbox and sends a pairing request if needed. * Adds the plumbing to get that request to host, and to get the response back to the web-app. * Saves the pairing response to local storage, and uses it next time we connect. * Uses Base64 throughout for the secret, since unencoded random strings can't be serialized via PPAPI. Note that pairing is still disabled because we're still missing per-platform Delegate implementations, a UI for revoking pairings, and policy support for disabling the feature. BUG=156182 Review URL: https://chromiumcodereview.appspot.com/16137004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203865 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/mach_override')
0 files changed, 0 insertions, 0 deletions