Manualshelf

User Manual

ManualsBrandsSensize ManualsElectronicsSensize Tracker v2 CAT-M
231232233234235236237238239240
Table Of Contents
SARA-R4 series-AT commands manual
UBX-17003787 - R16
20Device and data security
Page 239 of 401
Type Syntax Response Example
Set AT+USECPRF=<profile_id>,12,
<server_certificate>,<pinning_level>
OK AT+USECPRF=0,12,"my_srv_cert",0
OK
TLS session resumption
Set AT+USECPRF=<profile_id>,13,
<tag>,<param_val1>[,<param_
val2>]
OK AT+USECPRF=0,13,0,1
OK
Read AT+USECPRF=<profile_id>,13,<tag> +USECPRF: <profile_id>,13,<tag>,
<param_val1>[,<param_val2>]
OK
AT+USECPRF=0,13,0
+USECPRF: 0,13,0,1
OK
URC +UUSECPRF: <profile_id>,13,<tag>,
<param_val1>[,<param_val2>]
OK
+USECPRF: 0,13,1,0
OK
Test AT+USECPRF=? +USECPRF: (list of supported
<profile_id>s),(list of supported
<op_code>s)
OK
+USECPRF: (0-4),(0-13)
OK
20.3.3.3Defined values
Parameter Type Description
<profile_id> Number USECMNG security profile identifier, in range 0-4; if it is not followed by other parameters the
profile settings will be reset (set to factory-programmed value).
<op_code> Number
• 0: certificate validation level; allowed values for <param_val1>:
o 0 (factory-programmed value): level 0 - No validation; the server certificate will not be
checked or verified. The server in this case is not authenticated.
o 1: level 1 - Root certificate validation without URL integrity check. The server certificate will
be verified with a specific trusted certificates or with each of the imported trusted root
certificates.
o 2: level 2 - Root certificate validation with URL integrity check. Level 1 validation with an
additional URL integrity check.
o 3: level 3 - Root certificate validation with check of certificate validity date. Level 2
validation with an additional check of certificate validity date.
• 1: SSL/TLS/DTLS version to use; allowed values for <param_val1>:
o 0 (factory-programmed value): any; server can use any version for the connection.
o 1: TLSv1.0; connection allowed only to TLS/SSL servers which support TLSv1.0
o 2: TLSv1.1; connection allowed only to TLS/SSL servers which support TLSv1.1
o 3: TLSv1.2; connection allowed only to TLS/SSL servers which support TLSv1.2
• 2: cipher suite; allowed values for <param_val1> define which cipher suite will be used:
o 0 (factory-programmed value): (0x0000) Automatic the cipher suite will be negotiated in
the handshake process
o 1: (0x002f) TLS_RSA_WITH_AES_128_CBC_SHA
o 2: (0x003C) TLS_RSA_WITH_AES_128_CBC_SHA256
o 3: (0x0035) TLS_RSA_WITH_AES_256_CBC_SHA
o 4: (0x003D) TLS_RSA_WITH_AES_256_CBC_SHA256
o 5: (0x000a) TLS_RSA_WITH_3DES_EDE_CBC_SHA
o 6: (0x008c) TLS_PSK_WITH_AES_128_CBC_SHA
o 7: (0x008d) TLS_PSK_WITH_AES_256_CBC_SHA
o 8: (0x008b) TLS_PSK_WITH_3DES_EDE_CBC_SHA
o 9: (0x0094) TLS_RSA_PSK_WITH_AES_128_CBC_SHA
o 10: (0x0095) TLS_RSA_PSK_WITH_AES_256_CBC_SHA
o 11: (0x0093) TLS_RSA_PSK_WITH_3DES_EDE_CBC_SHA
o 12: (0x00ae) TLS_PSK_WITH_AES_128_CBC_SHA256
o 13: (0x00af) TLS_PSK_WITH_AES_256_CBC_SHA384
o 14: (0x00b6) TLS_RSA_PSK_WITH_AES_128_CBC_SHA256
o 15: (0x00b7) TLS_RSA_PSK_WITH_AES_256_CBC_SHA384
o 99: cipher suite selection using IANA enumeration, <byte_1> and <byte_2> are strings
containing the 2 bytes that compose the IANA enumeration, see Table 23.
• 3: trusted root certificate internal name;