Project

General

Profile

Actions

Bug #4713

closed

Unit tests encryptedBlob doesn't match the EncryptedContent spec

Added by Anonymous over 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
08/15/2018
Due date:
% Done:

100%

Estimated time:
0.50 h

Description

In the spec for EncryptedContent, the EncryptedPayload comes first:
https://github.com/named-data/name-based-access-control/blob/new/docs/spec.rst

EncryptedContent ::= ENCRYPTED-CONTENT-TYPE TLV-LENGTH
                       EncryptedPayload
                       InitializationVector?
                       EncryptedPayloadKey?
                       Name?

But in the unit tests encryptedBlobs, the InitializationVector comes first (which is TLV type 0x85):
https://github.com/named-data/name-based-access-control/blob/new/tests/tests/static-data.hpp#L50

8247
  8510DC331EF7FA210457DA66E482BFE1E7E1 // InitializationVector
  841048E10F2E5B32E25F82313FA65F2E83D7 // EncryptedPayload
  07210804736F6D650802636B08067072656669780802434B0809FD000001499D598CAA // Name

Is this a mismatch? Should either the spec or the unit test example be changed?

Actions #1

Updated by Junxiao Shi over 3 years ago

  • Status changed from New to Code review
  • Assignee set to Junxiao Shi
  • % Done changed from 0 to 100
  • Estimated time set to 0.50 h
Actions #2

Updated by Junxiao Shi over 3 years ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF