Hi Johan, > The conn->link_key variable tracks the type of link key in use. It is > set whenever we respond to a link key request as well as when we get a > link key notification event. > > These two events do not however always guarantee that encryption is > enabled: getting a link key request and responding to it may only mean > that the remote side has requested authentication but not encryption. On > the other hand, the encrypt change event is a certain guarantee that > encryption is enabled. The real encryption state is already tracked in > the conn->link_mode variable through the HCI_LM_ENCRYPT bit. > > This patch fixes a check for encryption in the hci_conn_auth function to > use the proper conn->link_mode value and thereby eliminates the chance > of a false positive result. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > net/bluetooth/hci_conn.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
