Added option for randompin_certificate 21/23721/2
authorMushfiqul Islam Antu <i.mushfiq@samsung.com>
Thu, 30 Nov 2017 12:25:31 +0000 (18:25 +0600)
committerMats Wichmann <mats@linux.com>
Sat, 9 Dec 2017 16:04:40 +0000 (16:04 +0000)
If a server supports both randompin and certificate
then the doxm.sct value should be 24, instead of
current default 16 on IoTivity.

Change-Id: I017bed18d3e0ad568b662a03d9bd80134538a8c3
Signed-off-by: Mushfiqul Islam Antu <i.mushfiq@samsung.com>
(cherry picked from commit 6888f190c2e8a1f9bd875dc3f6f362905488eadb)

resource/csdk/security/provisioning/sample/oic_svr_db_server_randompin.dat
resource/csdk/security/provisioning/sample/oic_svr_db_server_randompin.json

index 3049ee5..5a3f02e 100644 (file)
Binary files a/resource/csdk/security/provisioning/sample/oic_svr_db_server_randompin.dat and b/resource/csdk/security/provisioning/sample/oic_svr_db_server_randompin.dat differ
index ac8619f..90ac144 100644 (file)
@@ -53,7 +53,7 @@
     "doxm": {
         "oxms": [1],
         "oxmsel": 1,
-        "sct": 16,
+        "sct": 24,
         "owned": false,
         "deviceuuid": "87654321-4321-4321-4321-CBA987654321",
         "devowneruuid": "00000000-0000-0000-0000-000000000000",