Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
,Key version in case the key server signing key is rotated. (e.g. "v1") A PHA can only have one active public key at a time, so they must rotate keys on all devices and servers at the same time to avoid problems.
Implementation-specific string that can be used in key verification. Valid character in this string are all alphanumeric characters, underscores, and periods.
All keys must be signed using the SHA-256 with ECDSA algorithm. This field must contain the string "1.2.840.10045.4.3.2".
Used in:
Information to uniquely identify the public key associated with the key server's signing key.
Reserved for future use. Both batch_num and batch_size must be set to a value of 1.
Signature in X9.62 format (ASN.1 SEQUENCE of two INTEGER fields).
Information about associated signatures
Used in:
Temporary exposure key for an infected user.
Varying risk associated with a key depending on diagnosis method. Deprecated and no longer used.
The interval number since epoch for which a key starts
How long this key is valid, specified in increments of 10 minutes
defaults to 24 hours
Type of diagnosis associated with a key.
Number of days elapsed between symptom onset and the TEK being used. E.g. 2 means TEK is from 2 days after onset of symptoms. Valid values range is from -14 to 14.
Data type that represents why this key was published.
Used in:
Never returned by the client API.
Reserved for future use.
Used to revoke a key, never returned by client API.
Time window of keys in the file, based on arrival at the server, in UTC seconds.
The region from which these keys came
Reserved for future use. Both batch_num and batch_size must be set to a value of 1.
Information about associated signatures
Exposure keys that are new.
Keys that have changed status from previous key archives, including keys that are being revoked.