commit 98acbbf0924804beb3f0c2e4d9a96dc26c3fa458
author Arman Uguray <armansito@google.com> Thu Apr 25 20:35:33 2019 +0000
committer CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Thu Apr 25 20:35:33 2019 +0000
tree 38f3f853f09a94297b31fe25524d7111f1fda321
parent 96cc21c1432c3a2f3653e76934fc9a5b880cb425

[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