Comment 34 for bug 839157

This should now be fixed with a kernel patch. The 3.3 and newer contains the fix and for the stable
branches wait for those two commits to appear in the next release.

3.2-stable review patch. If anyone has any objections, please let me know.

------------------

From: Peter Hurley <email address hidden>

commit 18daf1644e634bae951a6e3d4d19d89170209762 upstream

Commit 330605423c fixed l2cap conn establishment for non-ssp remote
devices by not setting HCI_CONN_ENCRYPT_PEND every time conn security
is tested (which was always returning failure on any subsequent
security checks).

However, this broke l2cap conn establishment for ssp remote devices
when an ACL link was already established at SDP-level security. This
fix ensures that encryption must be pending whenever authentication
is also pending.

Signed-off-by: Peter Hurley <email address hidden>
Tested-by: Daniel Wagner <email address hidden>
Acked-by: Marcel Holtmann <email address hidden>
Signed-off-by: Johan Hedberg <email address hidden>

3.0-stable review patch. If anyone has any objections, please let me know.

------------------

From: Peter Hurley <email address hidden>

commit 18daf1644e634bae951a6e3d4d19d89170209762 upstream

Commit 330605423c fixed l2cap conn establishment for non-ssp remote
devices by not setting HCI_CONN_ENCRYPT_PEND every time conn security
is tested (which was always returning failure on any subsequent
security checks).

However, this broke l2cap conn establishment for ssp remote devices
when an ACL link was already established at SDP-level security. This
fix ensures that encryption must be pending whenever authentication
is also pending.

Signed-off-by: Peter Hurley <email address hidden>
Tested-by: Daniel Wagner <email address hidden>
Acked-by: Marcel Holtmann <email address hidden>
Signed-off-by: Johan Hedberg <email address hidden>