From: Johan Hedberg Date: Tue, 18 Mar 2014 13:42:30 +0000 (+0200) Subject: Bluetooth: Fix MITM flag when initiating SMP pairing X-Git-Tag: accepted/tizen/common/20141203.182822~316^2~18^2^2~46^2~5 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2e2336445e696805b40d6a13cf25f26d49e20069;p=platform%2Fkernel%2Flinux-arm64.git Bluetooth: Fix MITM flag when initiating SMP pairing The pairing process initiated through mgmt sets the conn->auth_type value regardless of BR/EDR or LE pairing. This value will contain the MITM flag if the local IO capability allows it. When sending the SMP pairing request we should check the value and ensure that the MITM bit gets correctly set in the bonding flags. Signed-off-by: Johan Hedberg Signed-off-by: Marcel Holtmann --- diff --git a/net/bluetooth/smp.c b/net/bluetooth/smp.c index 6f29430..a015003 100644 --- a/net/bluetooth/smp.c +++ b/net/bluetooth/smp.c @@ -909,6 +909,12 @@ int smp_conn_security(struct hci_conn *hcon, __u8 sec_level) authreq = seclevel_to_authreq(sec_level); + /* hcon->auth_type is set by pair_device in mgmt.c. If the MITM + * flag is set we should also set it for the SMP request. + */ + if ((hcon->auth_type & 0x01)) + authreq |= SMP_AUTH_MITM; + if (hcon->link_mode & HCI_LM_MASTER) { struct smp_cmd_pairing cp;