Skip to content

Commit 0017b22

Browse files
Final
1 parent 19868c3 commit 0017b22

File tree

1 file changed

+4
-7
lines changed
  • content/learning-paths/servers-and-cloud-computing/cca-trustee

1 file changed

+4
-7
lines changed

content/learning-paths/servers-and-cloud-computing/cca-trustee/flow.md

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -171,7 +171,7 @@ The request will fail with `Access denied by policy` and `Token Verifier` errors
171171
Error: request unauthorized
172172
```
173173

174-
## Evaluate the Attestation Result
174+
## Evaluate the Attestation result
175175

176176
In the previous step, the KBS failed to provide the requested secret. To understand why this happened, you need to learn more about how the attestation result is used to evaluate the trustworthiness of a CCA realm.
177177
In this step, you will examine the attestation result more closely.
@@ -190,16 +190,15 @@ If you spend more time on analyzing the message you will start seeing errors fro
190190
Using JWK key from JWT header
191191
Error: verifying signed EAR from "ear.jwt" using "JWK header" key: failed verifying JWT message: jwt.Parse: failed to parse token: jwt.Validate: validation failed: "exp" not satisfied: token is expired
192192
```
193-
194-
Please obtain a new EAR message by re-running the attestation command.
195193
{{% /notice %}}
196194

197195

198196
The `arc verify` command produces quite a lot of output.
197+
199198
However, the main part is the CCA attestation token that is similar to the one you inspected in
200199
[Get Started with CCA Attestation and Veraison](/learning-paths/servers-and-cloud-computing/cca-veraison) Learning Path.
201200

202-
Check the trustworthiness vectors near the end of the output. Example:
201+
Check the trustworthiness vectors near the end of the output:
203202

204203
```output
205204
[trustworthiness vectors]
@@ -214,9 +213,7 @@ Storage Opaque [none]: no claim being made
214213
Sourced Data [none]: no claim being made
215214
```
216215

217-
This part of the output shows how the attestation service has compared the attestation token against its expectations of a trustworthy system.
218-
These comparisons are known as "trustworthiness vectors".
219-
It also shows the conclusions that were drawn from that comparison.
216+
This part of the output shows how the attestation service has compared the attestation token against its expectations of a trustworthy system. These comparisons are known as *trustworthiness vectors"*. It also shows the conclusions that were drawn from that comparison.
220217

221218
Note these two trustworthiness vectors in the result:
222219
- __Hardware [affirming]__. Evidence in the attestation token shows a good match against the expectations of CCA platform.

0 commit comments

Comments
 (0)