Difference between revisions of "BLE AES128"
From Wiki Knowledge Base | Teltonika GPS
(Created page with "==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 ta...") |
m (Text replacement - "Bluetooth" to "Bluetooth®") |
||
(7 intermediate revisions by 2 users not shown) | |||
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 ''' | + | 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. | ||
− | [[Image:AES Serial Encrytpion.png]] | + | [[Image:AES Serial Encrytpion.png|center]] |
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. | 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. | ||
+ | |||
+ | [[Image:AES Serial Encrytpion set.png|center]] |
Latest revision as of 14:07, 6 December 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.
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.