TCG TSS 2.0 JSON 数据类型与策略语言规范

需积分: 1 109 浏览量更新于2024-06-22 收藏 1.36MB PDF 举报

"TSS_JSON_Policy_v0p7_r08_pub.pdf——这是一份关于TPM软件栈技术规范的文档，特别关注了TSS（Trusted Platform Module Software Stack）2.0版本中的JSON数据类型和策略语言的规范。该文档的版本为0.7，修订版为0.8，发布日期为2020年6月11日。由可信计算组（TCG）发布，旨在规定TPM软件栈中与安全相关的数据交互和政策定义。" 在TPM（Trusted Platform Module）软件栈中，TSS扮演着至关重要的角色。它提供了一组接口和机制，使得应用程序能够利用TPM硬件模块提供的安全服务。这些服务包括但不限于密钥管理、数字签名、验证平台状态等。JSON（JavaScript Object Notation）数据类型和策略语言是TSS2.0中用于描述和执行安全策略的重要组件。 JSON数据类型规范定义了如何在TPM操作中使用JSON格式来表示各种数据结构。这通常涉及到密钥参数、权限设置、证书等安全相关的信息。JSON是一种轻量级的数据交换格式，易于人阅读和编写，同时也易于机器解析和生成，因此是TSS中传递复杂安全信息的理想选择。策略语言则是用来描述TPM操作的条件和限制。例如，一个策略可能规定只有当平台处于特定的安全状态时，才能解密或签署数据。策略语言允许开发者精确地控制TPM的访问和使用，确保安全性的实现。在TSS2.0的上下文中，这些策略通常会涉及到JSON对象，以便于与其他系统组件进行交互。文档的免责声明指出，尽管这份规范提供了标准，但TCG并不对其实现或使用产生的任何问题负责，包括但不限于侵犯知识产权、损失利润、数据丢失等。这强调了使用者需要理解并接受潜在的风险，同时自行承担实施此规范带来的后果。这份"TPM软件栈技术规范"是关于如何在TPM环境中利用TSS2.0进行安全操作的详细指南，特别是关于JSON数据类型的处理和策略语言的运用，对于开发和维护依赖TPM安全功能的系统来说是必不可少的参考资料。

TCG TSS 2.0 JSON Data Types and Policy Language Specification

TCG TSS 2.0 JSON Data Types and Policy Language Specification | Version 0.7 | Revision 08 | 6/11/2020 | PUBLISHED Page 9 © TCG 2020

2 JSON encoding for TPM data types

This section provides a comprehensive list of transformation rules from TPM data type definitions (see TPM 2.0 Library

Specification Part 2 [12]) to JSON.

This specification sometimes allows multiple representations of the same data type. A parser SHALL support all of

these representations in order to allow human authors maximum flexibility. A serializer SHALL return one specific

version which will be denoted as the “normal form”.

2.1 TPM base types

2.1.1 UINT8 to INT32

The TPM base types UINT8, INT8, UINT16, INT16, UINT32, INT32 SHOULD be represented as JSON integers or

MAY be represented as JSON strings containing an integer in decimal or “0x” prefixed hex notation. JSON integers

have a size of 54 bits and are signed, which easily accommodates all of the above data types.

The normal form produced by TSS components SHOULD be a JSON integer.

This encoding SHALL also be used for typedefs and TPMI interface types derived from the base types. For example,

TPM2_HANDLE is represented the same as a UINT32.

Examples:

1 (normal form)

2 (normal form)

3 (normal form)

0x81000001

“1”

“0x8103ADce”

2.1.2 UINT64 and INT64

The TPM base types UINT64 and INT64 do not fit into the JSON integer representation. If the UINT64 or INT64 value

is small enough for a signed 54 bit representation, the JSON integer SHOULD be used. If the value does not fit into

the signed 54 bit representation, an array of two 32-bit values SHOULD be used – i.e. [ (value / (2^32)), (value %

(2^32)) ]. UINT64 and INT64 values MAY be represented as JSON strings containing an integer in decimal or “0x”-

prefix hex notation.

The normal form produced by TSS components SHOULD be a single JSON integer if the values are small enough or

a JSON array of two JSON integers containing the higher and low 32-bit values respectively.

Examples:

1 (normal form for <=54 signed bits)

“2”

“0x1234123412341234”

[ 123, 456 ] (normal form for >54 bits)

2.1.3 Named constants and Enumerations

Named constants and enumerations SHOULD be represented as a JSON string containing the value names from the

TPM 2.0 library Specification Part 2 with TPM2_ as a prefix. These value names SHOULD be shortened by removing

any TPM2_ prefixes or by removing their types’ name prefixes. The casing of the characters SHALL be ignored.

Alternatively, such values MAY be represented in the same way as the base types from which they derive as specified

in section 2.1.1.

The normal form produced by TSS components SHOULD be the shortened string representation as described in the

first paragraph of this subsection (section 2.1.3).

Examples:

TCG TSS 2.0 JSON Data Types and Policy Language Specification

TCG TSS 2.0 JSON Data Types and Policy Language Specification | Version 0.7 | Revision 08 | 6/11/2020 | PUBLISHED Page 10 © TCG 2020

“TPM2_RH_OWNER”

“RH_OWNER”

“OWNER” (normal form)

“0x40000001”

“TPM2_ALG_SHA1”

“ALG_SHA1”

“SHA1” (normal form)

“0x0004”

Data type aliases are treated as aliases for the purpose of this specification. Thus, the representation of a

TPM2_HANDLE is the same as that of a UINT32.

2.2 TPM2Bs byte buffer types

TPM2Bs are differentiated into simple TPM2Bs and complex TPM2Bs. Simple TPM2Bs are defined by the TPM types

specification as a size and a sized array of bytes. Complex TPM2Bs are defined as a size and an embedded TPMS

or TPMT.

2.2.1 Simple TPM2Bs

Simple TPM2Bs SHOULD be represented as JSON strings containing a BASE16 (HEX) representation of the byte

array (without any prefix), including any leading zeros. A prefix of “0x” MAY be prepended. The size field of the TPM2B

the length of the JSON string (without the prefix) divided by 2. Alternatively, a simple TPM2B MAY be represented as

a JSON array of JSON integers (one per byte) and the size inferred directly from the number of elements of the array.

The normal form produced by TSS components SHOULD be the JSON string representation without the prefix.

Examples:

“0a0d82fd00” (normal form)

“0x0a0d82fd0038283884849923982382389494”

[ 10, 22, 145, 21, 0, 123 ]

2.2.2 Complex TPM2Bs

Complex TPM2Bs do not have a JSON representation. Instead the TPMT or TPMS embedded in a complex TPM2B

SHALL be JSON encoded and inserted in place of the complex TPM2B.

Implementers note: When parsing a complex TPM2B field from JSON into a C data type as defined in the TCG TSS

Overview and Common Structures Specification [1], the size field of the complex TPM2B can be set to 0, since it is

ignored and inferred during marshaling, as described in the TCG TSS System API Specification [4].

Examples:

//TPM2B_ECC_POINT using the TPMS_ECC_POINT directly:

{

“x”: “1a2b3c”,

“y”: “4d5e6g”

}

2.3 TPML list types

A TPML type SHALL be represented as a JSON array. The size of the TPML type is inferred from the number of

elements of the JSON array.

Example:

//TPML_CC an array of TPM2_CC types:

[ “0x0000011f”, “TPM22_CC_EvictControl”, “HierarchyControl” ]

剩余56页未读，继续阅读

书香度年华

粉丝: 1w+
资源: 385

TCG TSS 2.0 JSON 数据类型与策略语言规范

TPM软件栈技术规范(TCG TSS RC v1.0 r12)发布

"TPM 软件栈技术规范 TSS版本1.2 Level 1详解

"TCG TSS SAPI v1.1r36规范详解与TPM软件栈技术

TSS_FAPI_v0p94_r09_pub.pdf

TCG_TSS_RC_v1p0_r12_pub.pdf

TCG_TSS_TCTI_v1p0_r18_pub.pdf

TCG_TSS_Marshaling_Unmarshaling_API_v1p0_r07_pub.pdf

TSS_2p0_TAB_ResourceManager_v1p0_r18_04082019_pub.pdf

TSS_Overview_Common_v1_r10_pub09232021.pdf

TSS_SAPI_v1p1_r36_pub10012021.pdf

最新资源