[PATCH v3 0/7] Handle link key type and security requirements

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Johan, 

I modified patch 6/7 according to your comment and have added a new patch 7/7 which is an
extension of mgmt api to require secure pin code.

Thanks,
Waldek

Waldemar Rymarkiewicz (7):
  Bluetooth: Add definitions for link key types
  Bluetooth: Don't modify sec_level if auth failed
  Bluetooth: Map sec_level to link key requirements
  Bluetooth: Ignore key unauthenticated for high security
  Bluetooth: Double check sec req for pre 2.1 device
  Bluetooth: Respect local MITM req in io_cap reply
  Bluetooth: Add secure flag for mgmt_pin_code_req

 include/net/bluetooth/hci.h      |    9 +++++
 include/net/bluetooth/hci_core.h |    3 +-
 include/net/bluetooth/mgmt.h     |    1 +
 net/bluetooth/hci_conn.c         |   61 +++++++++++++++++++++++++++++++------
 net/bluetooth/hci_core.c         |    2 +-
 net/bluetooth/hci_event.c        |   39 ++++++++++++++++++-----
 net/bluetooth/mgmt.c             |    3 +-
 net/bluetooth/rfcomm/core.c      |   17 ++++++++++-
 8 files changed, 112 insertions(+), 23 deletions(-)

--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux