Difference between revisions of "BLE AES128"

From Wiki Knowledge Base | Teltonika GPS
m (Protected "BLE AES128" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
m (Text replacement - "Bluetooth" to "Bluetooth®")
Line 1: Line 1:
 
==General Description==
 
==General Description==
  
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded.
+
Since this version '''03.27.07''' there has been an implementation of BLE transferred data encryption with '''AES128 cipher'''. In '''Bluetooth® 4.0 tab''' under '''Settings''' there is a field for a '''AES128 key'''. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded.
 
AES128 key field settings showed below.
 
AES128 key field settings showed below.
  

Revision as of 14:45, 27 October 2023

General Description

Since this version 03.27.07 there has been an implementation of BLE transferred data encryption with AES128 cipher. In Bluetooth® 4.0 tab under Settings there is a field for a AES128 key. Which if left empty, the BLE outgoing data will not be ciphered and incoming data will not be decoded. AES128 key field settings showed below.

AES Serial Encrytpion.png

If a key is present the outgoing data will be ciphered by the configured key and incoming data will be deciphered. The AES128 key must be in HEX format with a length of 16 bytes. As an example 11223344556677889900AABBCCDDEEFF is used.

AES Serial Encrytpion set.png