Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
,Key version for rollovers Must be in character class [a-zA-Z0-9_]. For example, 'v1'
Alias with which to identify public key to be used for verification Must be in character class [a-zA-Z0-9_.] For cross-compatibility with Apple, you can use your region's three-digit mobile country code (MCC). If your region has more than one MCC, choose the one that Apple has configured.
ASN.1 OID for Algorithm Identifier. For example, `1.2.840.10045.4.3.2'
Used in:
Info about the signing key, version, algorithm, etc. Only the verification_key_id, verification_key_version, and signature_algorithm fields within signature_info are read.
E.g., Batch 2 of 10 - these fields are ignored on android in favor of the batch fields within TemporaryExposureKeyExport
Signature in X9.62 format (ASN.1 SEQUENCE of two INTEGER fields)
Time window of keys in this batch based on arrival to server, in UTC seconds.
Region for which these keys came from, such as country.
For example, file 2 in batch size of 10. Ordinal, 1-based numbering. Note: Not yet supported on iOS.
Information about associated signatures
The TemporaryExposureKeys for initial release of keys. Keys should be included in this list for initial release, whereas revised or revoked keys should go in revised_keys.
TemporaryExposureKeys that have changed status. Keys should be included in this list if they have changed status or have been revoked.
Used in:
Key of infected user
Varying risk associated with a key depending on diagnosis method
The interval number since epoch for which a key starts
Increments of 10 minutes describing how long a key is valid
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 2 days after onset of symptoms.
Data type representing 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.