diff options
| author | joedow <joedow@chromium.org> | 2016-02-20 09:44:06 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-02-20 17:45:40 +0000 |
| commit | dadef9885e92560dfc56d7e4e227b2a5c421c02f (patch) | |
| tree | c5094be421d4b1fb5dd2d5bcc6f4a3a6126c4d32 /remoting/host/security_key | |
| parent | 46f64281f07fa102c1e0284c45826a4471b69572 (diff) | |
| download | chromium_src-dadef9885e92560dfc56d7e4e227b2a5c421c02f.zip chromium_src-dadef9885e92560dfc56d7e4e227b2a5c421c02f.tar.gz chromium_src-dadef9885e92560dfc56d7e4e227b2a5c421c02f.tar.bz2 | |
Updating webapp to send securityKey capability.
This change updates the CRD webapp to send the securityKey capability to
the host if the appropriate gnubby extension exists (which we would use
to resolve gnubby requests).
The only interesting bit in this change is that there is no synchronous
API to check for extension existence in Chrome (that I could find) so we
need to use a promise to wait for either a disconnect message or a
response to a Hello message to determine if the extension exists.
BUG=585835
Review URL: https://codereview.chromium.org/1707163002
Cr-Commit-Position: refs/heads/master@{#376654}
Diffstat (limited to 'remoting/host/security_key')
| -rw-r--r-- | remoting/host/security_key/gnubby_extension.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/remoting/host/security_key/gnubby_extension.cc b/remoting/host/security_key/gnubby_extension.cc index d225f31..156ffac 100644 --- a/remoting/host/security_key/gnubby_extension.cc +++ b/remoting/host/security_key/gnubby_extension.cc @@ -8,7 +8,7 @@ namespace { // TODO(joedow): Update this once clients support sending a gnubby capabililty. -// Tracked via: crbug.com/585835 +// Tracked via: crbug.com/587485 const char kCapability[] = ""; } |