15:12:12:253 TO2.HelloDevice started
15:12:12:253 eASigInfo write successful
15:12:12:253 TO2.HelloDevice completed successfully
15:12:12:253 fdo_prot_ctx_run Tx Request Body length: 51
15:12:12:253 fdo_prot_ctx_run Tx Request Body:
861907d050607dd20aea1f457090c95d8439ef34ae50d05726027fa4df6d36e65e8427dbe49a67454344483235361820822640
15:12:12:253 Proxy enabled but Not set
15:12:12:253 using DNS: 10.49.60.55
15:12:12:253 Resolving DNS-URL: <10.49.60.55>
15:12:12:256 Connect OK
15:12:12:256 Connecting to owner server
15:12:12:256 Proxy enabled but Not set
15:12:12:256 using IP
15:12:12:256 Connect OK
15:12:12:256
Sending REST header.

15:12:12:256 REST:header
15:12:12:256 http://10.49.60.55:8080/fdo/101/msg/60
15:12:12:256 HOST:10.49.60.55:8080
15:12:12:256 Content-type:application/cbor
15:12:12:256 Content-length:51
15:12:12:256 _connection: keep-alive
15:12:12:256
15:12:12:257 Parsing received Header.
15:12:12:257 REST: HTTP response line: HTTP/1.1 200 OK
15:12:12:257 Response code 200 received (OK)
15:12:12:257 Authorization: Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:257 Content type: application/cbor
15:12:12:257 Message-Type: 61
15:12:12:257 Body: Date
15:12:12:257 Content-length: 574
15:12:12:257 fdo_prot_ctx_run Rx Response Body:
8443a10126a219010050ed84b793a8310ec2e06e27686cedaaaa190101830a01585b3059301306072a8648ce3d020106082a8648ce3d03010703420004e89f5a02da3ce183cd8b72f17de749e8fb730fa951ff4ea48815594e27113ae80deebd43d37e4146dccbe5623ad46030650fb0095243c49831e608edfad721eb59017c8858c186186550607dd20aea1f457090c95d8439ef34ae8185820c4101820343191f9082054c6b31302e34392e36302e3535810e820443191f90653132333435830a01585b3059301306072a8648ce3d020106082a8648ce3d03010703420004e048d0cc68a12dcea21a266d5cbf6fce90dfb82c2d231e5977e060c329db9e148c2865ba6ac93300bea2f1a6731e125f71b59cff0fb865faeda6b57b5bfc29a6822f582043f5979bfb1b87067a0e83756e7953c06038e895704b196031d446b79587a2340182055820663c1fd44c91414a6fed578c4e79294a85cee0c8b3b333a00b9092048136c96a50d05726027fa4df6d36e65e8427dbe49a82264058560020fba63e0ca8b5ce6eb8ded840d05a24eb3d7486034b7bb51e7c9bc96bdcf20f250020ddff5a09744420044ba1ab884ea7ca6acc0b279ca7ed1a1943c32a3945f9a8c4001099a2b13a76e3ed3a0ce0f96cd095d768822f5820e392e9cf0b288ff037ebdbd016dd8a771f1ac53ea02298fd00fa9abb88ad2ec91907d0584078c9295868c62e491ee9648cf3b30136f671a8ee0e053e7e835f033594a23eeba0a37bd29df5618050e0de415700b49a9239c3d3b6b19c25d35b633ad19c9d3c
15:12:12:260 FDOProtTO2: Received message type 61 : 574 bytes
15:12:12:260 TO2.ProveOVHdr started
ERROR:[fdor_tag():898] CBOR decoder: Failed to read Tag
ERROR:[fdo_cose_read():3854] COSE: Failed to read/Invalid Tag
15:12:12:260 PublicKey.pkBody length: 91 bytes
15:12:12:260 Signature verifies OK.
15:12:12:260 TO2.ProveOVHdr: COSE signature verification successful
15:12:12:260 fdo_ov_hdr_read OVHeader read started!
15:12:12:260 There are 1 RendezvousDirective(s) in the RendezvousInfo
15:12:12:260 Processing RendezvousDirective Index 0
15:12:12:260 There are 5 RendezvousInstr(s)
15:12:12:260 Processing RendezvousInstr Index 0
15:12:12:261 Added RendezvousInstr entry 1
15:12:12:261 Processing RendezvousInstr Index 1
15:12:12:261 Added RendezvousInstr entry 2
15:12:12:261 Processing RendezvousInstr Index 2
15:12:12:261 Added RendezvousInstr entry 3
15:12:12:261 Processing RendezvousInstr Index 3
15:12:12:261 Added RendezvousInstr entry 4
15:12:12:261 Processing RendezvousInstr Index 4
15:12:12:261 Added RendezvousInstr entry 5
15:12:12:261 Added RendezvousDirective entry 1
15:12:12:261 RendezvousInfo read completed
15:12:12:261 PublicKey.pkBody length: 91 bytes
15:12:12:261 fdo_ov_hdr_read OVHeader read completed!
15:12:12:261 TO2.ProveOVHdr: OVHeader.OVPubKey hash verification successful
15:12:12:261 TO2.ProveOVHdr: Total number of OwnershipVoucher.OVEntries: 1
15:12:12:261 TO2.ProveOVHdr: Valid Ownership Header received
15:12:12:261 eBSigInfo read successful
15:12:12:261 Hash write completed
15:12:12:261 Hash write completed
15:12:12:261 TO2.ProveOVHdr completed. 1 OVEntry(s) to follow
15:12:12:261 TO2.GetOVNextEntry started
15:12:12:261 TO2.GetOVNextEntry completed successfully
15:12:12:261 fdo_prot_ctx_run Tx Request Body length: 2
15:12:12:261 fdo_prot_ctx_run Tx Request Body:
8100
15:12:12:261 Connecting to owner server
15:12:12:261 Proxy enabled but Not set
15:12:12:261 using IP
15:12:12:261 Connect OK
15:12:12:261
Sending REST header.

15:12:12:261 REST:header
15:12:12:261 http://10.49.60.55:8080/fdo/101/msg/62
15:12:12:261 HOST:10.49.60.55:8080
15:12:12:261 Content-type:application/cbor
15:12:12:261 Content-length:2
15:12:12:261 _connection: keep-alive
15:12:12:261 Authorization:Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:261
15:12:12:262 Parsing received Header.
15:12:12:262 REST: HTTP response line: HTTP/1.1 200 OK
15:12:12:262 Response code 200 received (OK)
15:12:12:262 Authorization: Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:262 Content type: application/cbor
15:12:12:262 Message-Type: 63
15:12:12:262 Body: Date
15:12:12:262 Content-length: 246
15:12:12:262 fdo_prot_ctx_run Rx Response Body:
82008443a10126a058aa84822f582028762ffd4a08e6443eb4561150b3692044b9d2767fb131845d57159dfd002cea822f58205f0861fd53ec54278730cc9390cd554f887549bc3e0212d354cac015d63690b7f6830a01585b3059301306072a8648ce3d020106082a8648ce3d03010703420004e89f5a02da3ce183cd8b72f17de749e8fb730fa951ff4ea48815594e27113ae80deebd43d37e4146dccbe5623ad46030650fb0095243c49831e608edfad721eb584045064867c2d9b4a805603b555f213e314593d7ea2e121f9773902c7f2b66f195ae1ac510609d25623940d5b070a63944fba27a2b9ed7722b8e971b8a3bc41911
15:12:12:263 FDOProtTO2: Received message type 63 : 246 bytes
15:12:12:263 TO2.OVNextEntry started
ERROR:[fdor_tag():898] CBOR decoder: Failed to read Tag
ERROR:[fdo_cose_read():3854] COSE: Failed to read/Invalid Tag
15:12:12:263 Signature verifies OK.
15:12:12:263 TO2.OVNextEntry: OVEntry Signature verification successful
15:12:12:263 PublicKey.pkBody length: 91 bytes
15:12:12:263 TO2.OVNextEntry: Verified OVEntry: 0
15:12:12:263 TO2.OVNextEntry: All 1 OVEntry(s) have been verified successfully!
15:12:12:263 TO2.ProveDevice started
15:12:12:263 Entity Attestation Token PayloadBaseMap: EATPayload to be written
15:12:12:263 TO2.ProveDevice: EATPayloadBaseMap created successfuly
15:12:12:263 TO2.ProveDevice comleted successfully
15:12:12:263 fdo_prot_ctx_run Tx Request Body length: 227
15:12:12:263 fdo_prot_ctx_run Tx Request Body:
d28443a10126a13901025021bdfbe7aa27debb50b7c7747efd6e185884a31901005101607dd20aea1f457090c95d8439ef34ae0a50ed84b793a8310ec2e06e27686cedaaaa390100815856002091919c2050b350a217e13b491e143cd62384a9e76eb5510ab1cd4fe1ddd6351f0020dffe1ab7053cf960ecaaee0237462df3763a2015fb8fdc79b0873cbb48eeb15a0010faccceee7e2aeaffb3f950a5b2b7d9135840e0bd11790b082587689bae6dc5dcc380ba33162dba7aaf0d26c078c71d2fa10c1e6b5dee55c47e73ad65bebe2f383a45bb653aa24c4d03c50a3a8367e5eb2cc2
15:12:12:264 Connecting to owner server
15:12:12:264 Proxy enabled but Not set
15:12:12:264 using IP
15:12:12:264 Connect OK
15:12:12:264
Sending REST header.

15:12:12:264 REST:header
15:12:12:264 http://10.49.60.55:8080/fdo/101/msg/64
15:12:12:264 HOST:10.49.60.55:8080
15:12:12:264 Content-type:application/cbor
15:12:12:264 Content-length:227
15:12:12:264 _connection: keep-alive
15:12:12:264 Authorization:Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:264
15:12:12:266 Parsing received Header.
15:12:12:266 REST: HTTP response line: HTTP/1.1 200 OK
15:12:12:266 Response code 200 received (OK)
15:12:12:266 Authorization: Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:266 Content type: application/cbor
15:12:12:266 Message-Type: 65
15:12:12:266 Body: Date
15:12:12:266 Content-length: 229
15:12:12:266 fdo_prot_ctx_run Rx Response Body:
8344a1011820a058dc4052a3062d5007a6011b9cb9b5a09b9ee32eef3a0f076b2a8c24f6853fc9ab93ce4cb2c3dd86f9e2d9ab1fc922a9be01ce315a72652e573026cf72c7ecb5625a2104886c3550848fccb41f6ca23d11b77f9da4c70a267f51f7198b0bbe51baedd47bfdf4ec72d4bccf7dece419da3ee52c25938bce019d07eff1c3161a32b06a98f0c85d5b5eadd867ba003ff5b248dbd361cdf3c6bcb462d4b6a159763615e302f62f39248b042ee472403886780bcb47d77595f15ff3e66915d0f7d643f3295b29d82ffe510f30f9fe738554580b181c863d99b0938b30ee96224c
15:12:12:266 FDOProtTO2: Received message type 65 : 229 bytes
15:12:12:266 TO2.SetupDevice started
ERROR:[fdor_tag():898] CBOR decoder: Failed to read Tag
ERROR:[fdo_cose_encrypt0_read():4481] COSE_Encrypt0: Failed to read/Invalid Tag
ERROR:[fdor_signed_int():820] CBOR decoder: Failed to read Major Type 1 (negative int)
ERROR:[fdo_cose_encrypt0_read_unprotected_header():4428] COSE_Encrypt0 Unprotected header: Failed to read AESIV Key
ERROR:[fdo_cose_encrypt0_read():4517] COSE_Encrypt0: Failed to read Unprotected header
ERROR:[fdo_encrypted_packet_read():2595] Encrypted Message Read: Failed to read COSE_Encrypt0
ERROR:[msg65():60] TO2.SetupDevice: Failed to parse encrypted packet
ERROR:[fdo_process_states():194] Error occurred while processing Type 65
ERROR:[fdo_send_error_message():409] Sending Error Message
15:12:12:267 fdo_prot_ctx_run Tx Request Body length: 39
15:12:12:267 fdo_prot_ctx_run Tx Request Body:
8518641841781a6d736736353a206d657373616765207061727365206572726f721a64e725f400
15:12:12:267 Connecting to owner server
15:12:12:267 Proxy enabled but Not set
15:12:12:267 using IP
15:12:12:267 Connect OK
15:12:12:267
Sending REST header.

15:12:12:267 REST:header
15:12:12:267 http://10.49.60.55:8080/fdo/101/msg/255
15:12:12:267 HOST:10.49.60.55:8080
15:12:12:267 Content-type:application/cbor
15:12:12:267 Content-length:39
15:12:12:267 _connection: keep-alive
15:12:12:267 Authorization:Bearer e02185b8-5a50-4636-8dc2-a1a75a78de48
15:12:12:267
15:12:12:267 Parsing received Header.
15:12:12:267 REST: HTTP response line: HTTP/1.1 405 Method Not Allowed
15:12:12:267 Response code 405 received (Method Not Allowed)
ERROR:[get_rest_content_length():481] HTTP reponse is not 200(OK)!
15:12:12:267 Body: Allow
15:12:12:267 Content type: text/plain; charset=utf-8
15:12:12:267 Body: X-Content-Type-Options
15:12:12:267 Body: Date
15:12:12:267 Content-length: 10
15:12:12:267 fdo_prot_ctx_run Rx Response Body:
726561642d6f6e6c790a
ERROR:[_STATE_TO2():1766] TO2 failed.