Bluetooth LE: Add support for Signed Write command.

- 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: Alex Blasche <alexander.blasche@theqtcompany.com>

1 files changed, 1 insertions, 0 deletions

diff --git a/qtconnectivity.pro b/qtconnectivity.pro
index 5eb864b8..4b7b9da9 100644
--- a/qtconnectivity.pro
+++ b/qtconnectivity.pro
@@ -3,4 +3,5 @@ require(!android|qtHaveModule(androidextras))
 load(configure)
 qtCompileTest(bluez)
 qtCompileTest(bluez_le)
+qtCompileTest(linux_crypto_api)
 load(qt_parts)