Hi Johan, > When a connection is requested the conn->pending_sec_level value gets > set to whatever level the user requested the connection to be. During > the pairing process there are various sanity checks to try to ensure > that the right length PIN or right IO Capability is used to satisfy the > target security level. However, when we finally get hold of the link key > that is to be used we should still set the actual final security level > from the key type. > > This way when we eventually get an Encrypt Change event the correct > value gets copied to conn->sec_level. > > Signed-off-by: Johan Hedberg <johan.hedberg@xxxxxxxxx> > --- > net/bluetooth/hci_event.c | 47 ++++++++++++++++++++++++++++++++++++++++------- > 1 file changed, 40 insertions(+), 7 deletions(-) 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
