1. 17 3月, 2015 1 次提交
  2. 15 3月, 2015 5 次提交
  3. 11 3月, 2015 1 次提交
  4. 07 3月, 2015 1 次提交
    • M
      Bluetooth: Introduce controller setting information for static address · 93690c22
      Marcel Holtmann 提交于
      Currently it is not possible to determine if the static address is used
      by the controller. It is also not possible to determine if using a
      static on a dual-mode controller with disabled BR/EDR is possible or
      not.
      
      To address this issue, introduce a new setting called static-address. If
      support for this setting is signaled that means that the kernel supports
      using static addresses. And if used on dual-mode controllers with BR/EDR
      disabled it means that a configured static address can be used.
      
      In addition utilize the same setting for the list of current active
      settings that indicates if a static address is configured and if that
      address will be actually used.
      
      With this in mind the existing Set Static Address management command
      has been extended to return the current settings. That way the caller
      of that command can easily determine if the programmed address will
      be used or if extra steps are required.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      93690c22
  5. 28 2月, 2015 1 次提交
  6. 03 2月, 2015 1 次提交
  7. 05 12月, 2014 1 次提交
  8. 03 12月, 2014 1 次提交
  9. 18 11月, 2014 1 次提交
  10. 31 7月, 2014 1 次提交
  11. 06 7月, 2014 1 次提交
  12. 05 7月, 2014 2 次提交
  13. 04 7月, 2014 2 次提交
  14. 03 7月, 2014 9 次提交
  15. 24 5月, 2014 1 次提交
  16. 16 5月, 2014 1 次提交
  17. 10 3月, 2014 1 次提交
  18. 28 2月, 2014 1 次提交
  19. 23 2月, 2014 1 次提交
  20. 20 2月, 2014 1 次提交
  21. 18 2月, 2014 1 次提交
  22. 13 2月, 2014 5 次提交
    • M
      Bluetooth: Rename authentication to key_type in mgmt_ltk_info · d40f3eef
      Marcel Holtmann 提交于
      The field is not a boolean, it is actually a field for a key type. So
      name it properly.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      d40f3eef
    • M
      Bluetooth: Add management command to allow use of debug keys · 4e39ac81
      Marcel Holtmann 提交于
      Originally allowing the use of debug keys was done via the Load Link
      Keys management command. However this is BR/EDR specific and to be
      flexible and allow extending this to LE as well, make this an independent
      command.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      4e39ac81
    • M
      Bluetooth: Add management setting for use of debug keys · b1de97d8
      Marcel Holtmann 提交于
      When the controller has been enabled to allow usage of debug keys, then
      clearly identify that in the current settings information.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      b1de97d8
    • M
      Bluetooth: Add support for remote OOB input of P-256 data · ec109113
      Marcel Holtmann 提交于
      The current management interface only allows to provide the remote
      OOB input of P-192 data. This extends the command to also accept
      P-256 data as well. To make this backwards compatible, the userspace
      can decide to only provide P-192 data or the combined P-192 and P-256
      data. It is also allowed to leave the P-192 data empty if userspace
      only has the remote P-256 data.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      ec109113
    • M
      Bluetooth: Add support for local OOB data with Secure Connections · 4d2d2796
      Marcel Holtmann 提交于
      For Secure Connections support and the usage of out-of-band pairing,
      it is needed to read the P-256 hash and randomizer or P-192 hash and
      randomizer. This change will read P-192 data when Secure Connections
      is disabled and P-192 and P-256 data when it is enabled.
      
      The difference is between using HCI Read Local OOB Data and using the
      new HCI Read Local OOB Extended Data command. The first one has been
      introduced with Bluetooth 2.1 and returns only the P-192 data.
      
      < HCI Command: Read Local OOB Data (0x03|0x0057) plen 0
      > HCI Event: Command Complete (0x0e) plen 36
            Read Local OOB Data (0x03|0x0057) ncmd 1
              Status: Success (0x00)
              Hash C from P-192: 975a59baa1c4eee391477cb410b23e6d
              Randomizer R with P-192: 9ee63b7dec411d3b467c5ae446df7f7d
      
      The second command has been introduced with Bluetooth 4.1 and will
      return P-192 and P-256 data.
      
      < HCI Command: Read Local OOB Extended Data (0x03|0x007d) plen 0
      > HCI Event: Command Complete (0x0e) plen 68
            Read Local OOB Extended Data (0x03|0x007d) ncmd 1
              Status: Success (0x00)
              Hash C from P-192: 6489731804b156fa6355efb8124a1389
              Randomizer R with P-192: 4781d5352fb215b2958222b3937b6026
              Hash C from P-256: 69ef8a928b9d07fc149e630e74ecb991
              Randomizer R with P-256: 4781d5352fb215b2958222b3937b6026
      
      The change for the management interface is transparent and no change
      is required for existing userspace. The Secure Connections feature
      needs to be manually enabled. When it is disabled, then userspace
      only gets the P-192 returned and with Secure Connections enabled,
      userspace gets P-192 and P-256 in an extended structure.
      
      It is also acceptable to just ignore the P-256 data since it is not
      required to support them. The pairing with out-of-band credentials
      will still succeed. However then of course no Secure Connection will
      b established.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NJohan Hedberg <johan.hedberg@intel.com>
      4d2d2796