0
edits
Changes
no edit summary
====2.2. SMS security:====
====2.2. SMS security:====
[[File:SMS Security.gif|alt=|border|SMS security|thumb|367x367px]]
[[File:SMS_Security.gif|alt=|thumb|450x450px|Set up sms secutiry]]
Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).
Essential fields in SMS/Call settings are Login and Password. The login and password are used with every SMS sent to FMB130. If login and password are not set, in every SMS sent to FMB125 device two spaces before command have to be used (<space><space><command>).
Command structure with set login and password:
Command structure with set login and password:
• at least 8 characters
• at least 8 characters
====2.5 BLE STANDARD AES-128====
====2.5 BLE STANDARD AES-128====
[[File:BLE STANDARD AES-128.gif|<big>BLE standart AES-128</big>|alt=|thumb|367x367px]]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.
[[File:BLE_STANDARD_AES-128.gif|alt=|center|frame]]
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.
==SECURE CONNECTION TO SERVER (TLS)==
==SECURE CONNECTION TO SERVER (TLS)==
[[File:TLS.gif|TLS/DTLS activate|alt=|thumb|367x367px]]In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.
[[File:TLS.gif|alt=|frame]]
In 03.27.07 base firmware version, Transport Layer Security TLS functionality has been updated and implemented for Teltonika GPS device series FMB0YX, FMB9X0, FMB1YX, FMU1YX, FMM1YX, FMC1YX, FMB2YX, and the model FMT100.
TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.
TLS is a cryptographic protocol that provides end-to-end security of data sent between server and tracker.
There are three main components to what the TLS protocol accomplishes: Encryption, Authentication, and Integrity.
There are three main components to what the TLS protocol accomplishes: Encryption, Authentication, and Integrity.
