6.10.2.15 ReleaseSigningKey
6.10.2.15.1 Purpose¶
The public half of a key that signs release information, so clients can check that it really comes from us. Keys follow The Update Framework (TUF), and each one belongs to a TUF role; the private half stays in a key management service (KMS) or a hardware security module (HSM).
6.10.2.15.2 Questions it answers¶
- Which keys can sign each metadata role?
- Is a key active, rotating or revoked?
6.10.2.15.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
role |
enum | 1..1 |
Values: root, targets, snapshot, timestamp. |
algorithm |
enum | 1..1 |
Values: ed25519, ecdsa_p256. |
public_key |
string |
1..1 |
|
kms_ref |
string |
1..1 |
|
status |
enum | 1..1 |
Values: active, rotating, revoked. |
validity |
Period | 1..1 |
|
created_at |
datetime |
1..1 |
|
updated_at |
datetime |
1..1 |
6.10.2.15.4 Relationships¶
Referenced by
ReleaseMetadataSignature.key(1..1)
Uses types
6.10.2.15.5 Rules & constraints¶
- Public key of a TUF role. The private key lives in a KMS or HSM, never in the database.