diff options
| author | Ravi Nagarajan <nravi@broadcom.com> | 2012-05-02 17:21:37 +0530 |
|---|---|---|
| committer | Matthew Xie <mattx@google.com> | 2012-07-14 11:19:19 -0700 |
| commit | defb69c3b383ad0f9b5d6329be625fafc2e3c931 (patch) | |
| tree | 1d13985bb9ca12b943aa70474a9a42243e6040a4 /btif/src/btif_sock_rfc.c | |
| parent | cff2b2b29bd9083f0b92e628b225a72a7ef52332 (diff) | |
| download | external_bluetooth_bluedroid-defb69c3b383ad0f9b5d6329be625fafc2e3c931.zip external_bluetooth_bluedroid-defb69c3b383ad0f9b5d6329be625fafc2e3c931.tar.gz external_bluetooth_bluedroid-defb69c3b383ad0f9b5d6329be625fafc2e3c931.tar.bz2 | |
Resolve JustWorks related pairing issues
1. Per the spec, if both sides are using "No Bonding" for auth requirements, then the key could be considered a session key. Updated the pairing logic to handle this
2. If incoming JustWorks pairing is initiated, prompt the user for consent if the peer's io capabilities reflects DisplayOnly or NoInputNoOutput
Change-Id: If592c96203e7a4b25af3d87056d534131b606e58
Diffstat (limited to 'btif/src/btif_sock_rfc.c')
0 files changed, 0 insertions, 0 deletions