BLE AES128 - Revision history

Arnas.Zeb: Text replacement - "Bluetooth" to "Bluetooth®"

2023-12-06T12:07:14Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 15:07, 6 December 2023
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.

Jonas.sterbavicius: Text replacement - "Bluetooth®" to "Bluetooth"

2023-10-27T13:44:57Z

Text replacement - "Bluetooth®" to "Bluetooth"

← Older revision		Revision as of 16:44, 27 October 2023
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.

Jonas.sterbavicius: Text replacement - "Bluetooth" to "Bluetooth®"

2023-10-27T13:07:27Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 16:07, 27 October 2023
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.

Jonas.sterbavicius: Text replacement - "Bluetooth®" to "Bluetooth"

2023-10-27T12:56:47Z

Text replacement - "Bluetooth®" to "Bluetooth"

← Older revision		Revision as of 15:56, 27 October 2023
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.

Jonas.sterbavicius: Text replacement - "Bluetooth" to "Bluetooth®"

2023-10-27T12:45:49Z

Text replacement - "Bluetooth" to "Bluetooth®"

← Older revision		Revision as of 15:45, 27 October 2023
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.

Tomas.kriauciunas: Protected "BLE AES128" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2021-07-26T11:21:19Z

Protected "BLE AES128" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision		Revision as of 14:21, 26 July 2021
(No difference)

Tomas.kriauciunas: /* General Description */

2021-07-26T11:18:54Z

General Description

← Older revision		Revision as of 14:18, 26 July 2021
Line 7:		Line 7:

	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]]

Tomas.kriauciunas at 11:17, 26 July 2021

2021-07-26T11:17:03Z

← Older revision		Revision as of 14:17, 26 July 2021
Line 4:		Line 4:
	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.

Tomas.kriauciunas: 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..."

2021-07-26T11:16:38Z

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..."

New page

==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.

[[Image: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.