Difference between revisions of "AES128 BLE Encryption testing"

From Wiki Knowledge Base | Teltonika Mobility
Line 10: Line 10:
 
#For <b>BLE Encryption</b> feature we need to download the [https://wiki.teltonika-mobility.com/wikibase/images/b/b8/Simple_BLE_Terminal.zip Simple BLE Terminal].<br>
 
#For <b>BLE Encryption</b> feature we need to download the [https://wiki.teltonika-mobility.com/wikibase/images/b/b8/Simple_BLE_Terminal.zip Simple BLE Terminal].<br>
 
#Using the <b>Teltonika Configurator</b> in <b>Bluetooth</b> section, make sure that <b>BT Radio</b> is Enabled (visible). Also in this section <b>Local Name</b> and <b>Local PIN</b> of the device can be seen.<br><br>[[Image:Confblue.png|700px|center]]<br>
 
#Using the <b>Teltonika Configurator</b> in <b>Bluetooth</b> section, make sure that <b>BT Radio</b> is Enabled (visible). Also in this section <b>Local Name</b> and <b>Local PIN</b> of the device can be seen.<br><br>[[Image:Confblue.png|700px|center]]<br>
#After the download has been completed, press scan and from provided BLE devices list choose the one that needs to be tested.<br><br>[[Image:Scantft.png|300px|center]]<br>
+
#After the configuration of device and download of Simple BLE terminal has been completed, press scan and from provided BLE devices list choose the one that needs to be tested.<br><br>[[Image:Scantft.png|300px|center]]<br>
 
#Using <b>Teltonika Configurator</b> open <b>Bluetooth 4.0</b> section and in <b>BLE Encryption Key</b> input field type in the <b>AES Key</b> that you would like to use. <b>BLE Encryption Key</b> have to be a 16 byte hex coded string. Example of <b>AES Key:</b> 00112233445566778899AABBCCDDEEFF.<br><br>[[Image:Confaes128.png|300px|center]]<br>
 
#Using <b>Teltonika Configurator</b> open <b>Bluetooth 4.0</b> section and in <b>BLE Encryption Key</b> input field type in the <b>AES Key</b> that you would like to use. <b>BLE Encryption Key</b> have to be a 16 byte hex coded string. Example of <b>AES Key:</b> 00112233445566778899AABBCCDDEEFF.<br><br>[[Image:Confaes128.png|300px|center]]<br>
 
#Configure the <b>AES Key</b> in the <b>Simple BLE Terminal</b> by pressing three dots in the top right corner.<br><br>[[Image:BLE terminal ciphered.png|300px|center]]<br>
 
#Configure the <b>AES Key</b> in the <b>Simple BLE Terminal</b> by pressing three dots in the top right corner.<br><br>[[Image:BLE terminal ciphered.png|300px|center]]<br>

Revision as of 17:13, 25 March 2022

Main Page > FAQ > TFT100 FAQ > AES128 BLE Encryption testing

AES128 BLE Encryption testing



NOTE! AES128 BLE Encryption feature is only available on 55.01.06.Rev.00 FW or newer.


If BLE Encryption Key is set, then device will communicate over BLE SPP (Serial Port Profile) with AES cipher mechanism. All incoming and outgoing data will be crypted with AES128 algorithm with entered key. Connected to the other side device must have similar encryption method and algorithm BLE Encryption Key is a 16 byte hex coded string.

  1. For BLE Encryption feature we need to download the Simple BLE Terminal.
  2. Using the Teltonika Configurator in Bluetooth section, make sure that BT Radio is Enabled (visible). Also in this section Local Name and Local PIN of the device can be seen.

    Confblue.png

  3. After the configuration of device and download of Simple BLE terminal has been completed, press scan and from provided BLE devices list choose the one that needs to be tested.

    Scantft.png

  4. Using Teltonika Configurator open Bluetooth 4.0 section and in BLE Encryption Key input field type in the AES Key that you would like to use. BLE Encryption Key have to be a 16 byte hex coded string. Example of AES Key: 00112233445566778899AABBCCDDEEFF.

    Confaes128.png

  5. Configure the AES Key in the Simple BLE Terminal by pressing three dots in the top right corner.

    BLE terminal ciphered.png

  6. Use the same AES Key, that have been typed in before into Teltonika Configurator.

    AESkey.png

  7. After the AES Key is configured and device is successfully connected to the Simple BLE Terminal, we can type in the command we want to send adding @sms_run: before the command.

    Commandsent.png

Alert.png

If the BLE Encryption Key does not match - response to sent command will not be received.

Nocommands.png