aboutsummaryrefslogtreecommitdiffstats
path: root/api
diff options
context:
space:
mode:
authorSven Gothel <[email protected]>2020-12-10 07:02:10 +0100
committerSven Gothel <[email protected]>2020-12-10 07:02:10 +0100
commitab86d222890076ce26b8638411e490c047add780 (patch)
treedd7f37fc70f35fe2278b9b001d2741d00819ac97 /api
parent118d564141d594e3f9fe0a082f1854289c95a7a8 (diff)
BluetoothDevice: Support SMPLongTermKeyInfo via [get/set]LongTermKeyInfo(..), tested with DBTScanner10.java
Java + Native test are now on par, may share the LTK binary file in example. On loading a pre-existing key when device found and before connecting, BlueZ/Kernel will try the uploaded key and no pairing procedure is being performed. This tested with explicit unpair before uploading the LTK, to ensure the pre-existing keys have been deleted.
Diffstat (limited to 'api')
-rw-r--r--api/direct_bt/DBTDevice.hpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/api/direct_bt/DBTDevice.hpp b/api/direct_bt/DBTDevice.hpp
index 3239dc63..a870dfd2 100644
--- a/api/direct_bt/DBTDevice.hpp
+++ b/api/direct_bt/DBTDevice.hpp
@@ -448,7 +448,7 @@ namespace direct_bt {
/**
* Returns a copy of the long term ket (LTK) info, valid after connection and SMP pairing has been completed.
* @param responder true will return the responder's LTK info (remote device, LL slave), otherwise the initiator's (the LL master).
- * @return
+ * @return the resulting key. SMPLongTermKeyInfo::enc_size will be zero if invalid.
* @see ::SMPPairingState::COMPLETED
* @see AdapterStatusListener::deviceReady()
*/