Changes

2 bytes removed ,  16:02, 9 December 2021
no edit summary
Line 96: Line 96:  
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.
 
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.
 
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.
[[File:BLE STANDARD AES-128.gif|center|<big>BLE standart AES-128</big>|alt=|thumb|500x500px]]
+
[[File:BLE STANDARD AES-128.gif|<big>BLE standart AES-128</big>|alt=|thumb|500x500px|left]]
 
==SECURE CONNECTION TO SERVER (TLS)==
 
==SECURE CONNECTION TO SERVER (TLS)==
  
Anonymous user

Navigation menu