Skip to content

chore: refactor for use in Veraison book #62

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 24, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions api/challenge-response/README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
# Interaction models
# Challenge/Response

## Interaction models

The APIs described here are meant to be instantiations of the abstract
protocols described in [Reference Interaction Models for Remote Attestation
Procedures](https://datatracker.ietf.org/doc/draft-ietf-rats-reference-interaction-models/).

## Challenge/Response
## Session flow

Each Challenge-Response session is associated to its own resource, with the
following attributes:
Expand Down
4 changes: 2 additions & 2 deletions api/endorsement-provisioning/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -91,12 +91,12 @@ format is CoRIM.
{ "status": "processing|success|failed" }
```


* Client submits the endorsement provisioning request
* Server responds with response code `201` indicating that the request has been accepted and will be processed asynchronously
* Server returns the URI of a time-bound session resource in the `Location` header. The resource can be polled at regular intervals to check the progress of the submission, until the processing is complete (either successfully or with a failure)

### Example

### Example

```text
>> Request:
Expand Down
2 changes: 1 addition & 1 deletion api/management/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ The API described here are intended to assist with the operation and management
of a Veraison services deployment. They are not meant to be utilized by the
services' users.

## Policy management
# Policy management

Policies allow augmenting attestation scheme generated [Attestation Results] on
per-deployment basis, by specifying additional rules to be applied to these
Expand Down
7 changes: 5 additions & 2 deletions repo-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,12 +31,15 @@ Veraison services expose REST APIs. This set of libraries provides convenient co
This collection of libraries provides manipulation and verification functionality for Attestation formats of various architectures.

[psatoken](https://github.com/veraison/psatoken): Platform Security Abstraction (PSA) Attestation Token manipulation library.

[ccatoken](https://github.com/veraison/ccatoken)
A library for the Arm Confidential Computing Architecture (CCA) Attestation Token.

[dice](https://github.com/veraison/dice): library providing support functions for manipulating various profiles of DICE.

[parsec](https://github.com/veraison/parsec): Library support for handling the Parsec Key Attestation formats used in the attested TLS PoC.
[enact-demo](https://github.com/veraison/enact-demo): EnactTrust TPM/Veraison interop demo and related docs

[enact-demo](https://github.com/veraison/enact-demo): EnactTrust TPM/Veraison interop demo and related docs


## CLI tools
Expand Down Expand Up @@ -200,4 +203,4 @@ subgraph Veraison["<b>Administrative Repositories</b>"]
VA
end

```
```