You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This only works correctly when the JSON data returned by the PCS always follows the same order, which seems to be no longer the case.
It is also not guaranteed by the JSON specification.
To quote from the specification:
JSON is built on two structures:
A collection of name/value pairs. In various languages, this is realized as an object, record, struct, dictionary, hash table, keyed list, or associative array.
An ordered list of values. In most languages, this is realized as an array, vector, list, or sequence.
Since the PCS does not return an ordered list (array), but a collection of name/value pairs, the PccsAdminTool should not depend on the ordering of said values.
The text was updated successfully, but these errors were encountered:
The PccsAdminTool does not follow the JSON specification when parsing the response of the PCS when retrieving QE/QVE/TD_QE identity.
Specifically this section performs manual parsing of the JSON data:
SGXDataCenterAttestationPrimitives/tools/PccsAdminTool/lib/intelsgx/pcs.py
Lines 691 to 697 in fa6631c
This code only works correctly when the response is ordered like the following:
This only works correctly when the JSON data returned by the PCS always follows the same order, which seems to be no longer the case.
It is also not guaranteed by the JSON specification.
To quote from the specification:
Since the PCS does not return an ordered list (array), but a collection of name/value pairs, the PccsAdminTool should not depend on the ordering of said values.
The text was updated successfully, but these errors were encountered: