Skip to content

docs: fix kms rpc proto link #386

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.

Sign up for GitHub

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
kvinwang merged 1 commit into from
Nov 5, 2025
Merged

docs: fix kms rpc proto link #386

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions kms/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ The verification process follows these steps:

## The RPC Interface

The KMS RPC interface is defined in [kms.proto](rpc/proto/kms.proto).
The KMS RPC interface is defined in [kms_rpc.proto](rpc/proto/kms_rpc.proto).

The core interface serving the dstack app are:
- `GetAppKey`: Requests an app key using the app ID and TDX quote
Expand All @@ -171,7 +171,7 @@ The `GetAppKey` RPC is used by the dstack app to request an app key. In this RPC


Note:
There are multiple keys derived for different usage, see [kms.proto](rpc/proto/kms.proto) for more details.
There are multiple keys derived for different usage, see [kms_rpc.proto](rpc/proto/kms_rpc.proto) for more details.
The root key is generated by a genesis KMS node in TEE and would be stored in the KMS node's encrypted local disk, replicated to other KMS nodes.
The keys are derived with app id which guarantees apps can not get the keys from other apps.

Expand Down