Skip to content
Snippets Groups Projects
Commit 98acbbf0 authored by Arman Uguray's avatar Arman Uguray Committed by CQ bot account: commit-bot@chromium.org
Browse files

[bt][gap] Distribute local identity information during pairing

LowEnergyConnectionManager now responds to local identity information
requests during the feature exchange and key distribution phases of SMP
pairing.

Bug: BT-243 #done
Test: 1. Run bt-pairing-tool, bt-le-battery-peripheral, and
         bt-le-peripheral -c -n <NAME> on Fuchsia. This will put Fuchsia
	 into LE peripheral mode with one GATT service that requires
	 security.
      2. Connect to Fuchsia from iOS using the nRF Connect app. This
         should trigger LE pairing. Respond to the authentication challenge
	 using bt-pairing-tool (local passkey entry on ToT). The battery
	 service characteristic should be readable and notifiable
	 without any errors.
      3. Pipe the output of bt-snoop-cli to Wireshark and confirm that:
         a. Fuchsia configured advertising using a random address.
	 b. Local IRK and identity address were distributed over SMP.
	 Check that the IRK matches what has been persisted in the
	 stash. Check that the identity address matches the address of
	 the active adapter (confirm via bt-cli).
      4. Reboot Fuchsia, repeat step #1. Connect again using nRF
         Connect. The battery service should be accessible without
	 additional pairing errors.
      5. Check the snoop logs to confirm that Fuchsia used a different
         RPA when advertising.
Change-Id: Ibb78b2de3049f9f351215ed4d878acfcca5569df
parent 96cc21c1
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment