OSDN Git Service

Bluetooth: Add support for storing the key size
authorVinicius Costa Gomes <vinicius.gomes@openbossa.org>
Fri, 8 Jul 2011 21:31:45 +0000 (18:31 -0300)
committerJaikumar Ganesh <jaikumar@google.com>
Mon, 11 Jul 2011 18:59:36 +0000 (11:59 -0700)
commit1fa2de3b1af303eb0b1c04c302bb5f62b4b4c596
tree26a788bfdf77db48c075fb62fc51caafab5e2815
parentc00ddbfadcdc5d0d26aa2ba54fa3ba1c5226b35c
Bluetooth: Add support for storing the key size

In some cases it will be useful having the key size used for
encrypting the link. For example, some profiles may restrict
some operations depending on the key length.

The key size is stored in the key that is passed to userspace
using the pin_length field in the key structure.

For now this field is only valid for LE controllers. 3.0+HS
controllers define the Read Encryption Key Size command, this
field is intended for storing the value returned by that
command.

Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
include/net/bluetooth/hci_core.h
net/bluetooth/hci_core.c
net/bluetooth/hci_event.c
net/bluetooth/mgmt.c
net/bluetooth/smp.c