diff options
author | Johan Hedberg <johan.hedberg@intel.com> | 2014-06-09 10:58:14 (GMT) |
---|---|---|
committer | Marcel Holtmann <marcel@holtmann.org> | 2014-06-13 11:30:42 (GMT) |
commit | ba15a58b179ed76a7e887177f2b06de12c58ec8f (patch) | |
tree | a068dd339dc86cfb402737c26853626bb8742ccc /drivers/oprofile | |
parent | e694788d73efe139b24f78b036deb97fe57fa8cb (diff) | |
download | linux-ba15a58b179ed76a7e887177f2b06de12c58ec8f.tar.xz |
Bluetooth: Fix SSP acceptor just-works confirmation without MITM
From the Bluetooth Core Specification 4.1 page 1958:
"if both devices have set the Authentication_Requirements parameter to
one of the MITM Protection Not Required options, authentication stage 1
shall function as if both devices set their IO capabilities to
DisplayOnly (e.g., Numeric comparison with automatic confirmation on
both devices)"
So far our implementation has done user confirmation for all just-works
cases regardless of the MITM requirements, however following the
specification to the word means that we should not be doing confirmation
when neither side has the MITM flag set.
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Tested-by: Szymon Janc <szymon.janc@tieto.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
Cc: stable@vger.kernel.org
Diffstat (limited to 'drivers/oprofile')
0 files changed, 0 insertions, 0 deletions