1. 08 Apr, 2016 - 1 commit
  2. 05 Apr, 2016 - 1 commit
  3. 04 Apr, 2016 - 1 commit
  4. 23 Mar, 2016 - 1 commit
  5. 22 Mar, 2016 - 2 commits
  6. 21 Mar, 2016 - 1 commit
  7. 18 Mar, 2016 - 1 commit
  8. 17 Mar, 2016 - 1 commit
  9. 15 Mar, 2016 - 1 commit
  10. 09 Mar, 2016 - 1 commit
  11. 07 Mar, 2016 - 1 commit
  12. 04 Mar, 2016 - 1 commit
  13. 25 Feb, 2016 - 3 commits
  14. 23 Feb, 2016 - 4 commits
  15. 17 Feb, 2016 - 2 commits
  16. 16 Feb, 2016 - 1 commit
  17. 15 Feb, 2016 - 1 commit
  18. 12 Feb, 2016 - 1 commit
  19. 11 Feb, 2016 - 1 commit
  20. 10 Feb, 2016 - 2 commits
  21. 09 Feb, 2016 - 3 commits
  22. 08 Feb, 2016 - 1 commit
  23. 05 Feb, 2016 - 1 commit
  24. 04 Feb, 2016 - 1 commit
  25. 03 Feb, 2016 - 1 commit
    • Christian Kandeler's avatar
      Bluetooth LE: Add support for Signed Write command. · c516f615
      Christian Kandeler authored
      
      - This is how we get at the signature resolving key:
          1) On connection from a client, we read the key from the
             respective BlueZ settings file (BlueZ 5 only, as I did
             not manage to find out where BlueZ 4 keeps this information).
          2) Also monitor the HCI traffic for key updates (due to re-pairing).
      - While there is an autotest for the actual hashing procedure, the
        overall feature cannot be easily tested for various reasons (there is
        no signed write support in our client API, for one). However, to help
        with manual testing, the server part of our autotest now exposes a
        characteristic that supports signed writes.
      - This feature requires a Linux kernel >= 3.7.
      
      Change-Id: I7ede9b430de167fe1f4519eedf8670d88d79aa25
      Reviewed-by: default avatarAlex Blasche <alexander.blasche@theqtcompany.com>
      c516f615
  26. 02 Feb, 2016 - 2 commits
  27. 27 Jan, 2016 - 2 commits
  28. 26 Jan, 2016 - 1 commit