Changes

TRACKER’S SECURITY (view source)

Revision as of 16:57, 2 December 2021

34 bytes added ,  16:57, 2 December 2021
no edit summary
Line 34: Line 34:     
====2.1. Set up Keyword:====
 
====2.1. Set up Keyword:====
−
[[File:Keyword use.gif|thumb|480x480px|alt=|Set up keyword]]
+
[[File:Keyword use.gif|thumb|312x312px|alt=|Set up keyword]]
      Line 55: Line 55:     
This command will emove existing keyword. If device is locked, keyword cannot be changed.   
 
This command will emove existing keyword. If device is locked, keyword cannot be changed.   
−
  −
         
====2.2. SMS security:====
 
====2.2. SMS security:====
−
[[File:SMS Security.gif|left|alt=|border|frame|SMS security]]
+
[[File:SMS Security.gif|left|alt=|border|SMS security|thumb|450x450px]]
−
 
  −
 
      
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>).
Line 92: Line 88:  
• at least one lowercase letter
 
• at least one lowercase letter
 
• at least 8 characters
 
• at least 8 characters
−
  −
   
====2.5 BLE STANDARD AES-128====
 
====2.5 BLE STANDARD AES-128====
    
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|frame|<big>BLE standart AES-128</big>]]
+
[[File:BLE STANDARD AES-128.gif|center|<big>BLE standart AES-128</big>|alt=|thumb|500x500px]]
 
==SECURE CONNECTION TO SERVER (TLS)==
 
==SECURE CONNECTION TO SERVER (TLS)==
   Line 111: Line 105:     
All preparation describe in the [https://wiki.teltonika-gps.com/wikibase/images/4/4e/FMBXX_TLSDTLS_encryption_configuration_v0.3.pdf TLS/DTLS prepare guide] in the device you need activate this
 
All preparation describe in the [https://wiki.teltonika-gps.com/wikibase/images/4/4e/FMBXX_TLSDTLS_encryption_configuration_v0.3.pdf TLS/DTLS prepare guide] in the device you need activate this
−
[[File:TLS.gif|center|frame|TLS/DTLS activate]]
+
[[File:TLS.gif|center|TLS/DTLS activate|alt=|thumb|450x450px]]
Anonymous user
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/68941"

Navigation menu