Bluetooth: Fix setting correct security level when initiating SMP
authorJohan Hedberg <johan.hedberg@intel.com>
Thu, 18 Sep 2014 08:26:32 +0000 (11:26 +0300)
committerMarcel Holtmann <marcel@holtmann.org>
Thu, 18 Sep 2014 15:39:37 +0000 (17:39 +0200)
commit5eb596f55cacc2389554a8d7572d90d5e9d4269d
treebf28b3dda0666f703a7db043049f90aa96879c3c
parent0097db06f5ab2df1756bc4cbf4395593024d87a1
Bluetooth: Fix setting correct security level when initiating SMP

We can only determine the final security level when both pairing request
and response have been exchanged. When initiating pairing the starting
target security level is set to MEDIUM unless explicitly specified to be
HIGH, so that we can still perform pairing even if the remote doesn't
have MITM capabilities. However, once we've received the pairing
response we should re-consult the remote and local IO capabilities and
upgrade the target security level if necessary.

Without this patch the resulting Long Term Key will occasionally be
reported to be unauthenticated when it in reality is an authenticated
one.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Cc: stable@vger.kernel.org
net/bluetooth/smp.c