covid19/cwa-documentation
covid19/cwa-documentation
1
0
Fork 0
mirror of https://github.com/corona-warn-app/cwa-documentation synced 2024-12-28 23:51:56 +01:00
Code Releases Activity

Merge pull request #577 from corona-warn-app/event-registration

Browse Source 
Event Registration: use base64url instead of base64 in QR code
This commit is contained in:
Maximilian Lenkeit 2021-04-07 08:02:56 +02:00 committed by GitHub
commit 441b3ed5a5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
event_registration.md
View File

@ -54,7 +54,7 @@ However, we acknowledge that this does not prevent to execute this attack for a
## QR Code Structure DRAFT
The QR code of a venue contains all required attributes for Presence Tracing, so that no server communication is necessary when an attendee checks in to a venue
The QR code of a venue contains all required attributes for Presence Tracing, so that no server communication is necessary when an attendee checks in to a venue.
The data structure is described by the Protocol Buffer message `QRCodePayload`:
@ -113,25 +113,25 @@ message CWALocationData {
}
```
The ID of a venue is derived as the SHA-256 hash of the concatenated byte representation of the string `CWA-GUID` and the byte representation of the Protocol Buffer message `QRCodePayload`. The `cryptographicSeed` adds sufficient entropy so that any modifications to the QR result in a unique ID.
The ID of a venue is derived as the SHA-256 hash of the concatenated byte representation of the string `CWA-GUID` and the byte representation of the Protocol Buffer message `QRCodePayload`. The `cryptographicSeed` adds sufficient entropy so that any modifications to the QR code result in a unique ID.
A `QRCodePayload` is base64-encoded and included in a URL. The URL is the content of the QR code and structures as follows:
A `QRCodePayload` is base64url-encoded and included in a URL. The URL is the content of the QR code and has the following structure:
```text
https://e.coronawarn.app?v=1#<base64_encoded>
https://e.coronawarn.app?v=1#<base64url_encoded>
# example:
CWA Germany:
https://e.coronawarn.app?v=1#Y3dh...
NotifyMe CH:
https://qr.notify-me.ch?v=2#bm90aWZ5bWU=
https://qr.notify-me.ch?v=2#bm90aWZ5bWU
CLEA FR:
https://tac.gouv.fr?v=1#Y2xlYQ==
https://tac.gouv.fr?v=1#Y2xlYQ
```
### QR Code Compatibility with Other Contract Tracing Apps in Germany DRAFT
Other contact tracing apps in Germany that leverage QR code for Presence Tracing can integrate with CWA by creating QR codes according to the following pattern:
Other contact tracing apps in Germany that leverage QR codes for Presence Tracing can integrate with CWA by creating QR codes according to the following pattern:
```text
<URL>/<VENDOR_DATA>#[VENDOR_ADDITIONAL_DATA]/CWA1/<ENCODED_PAYLOAD>
@ -142,7 +142,7 @@ Other contact tracing apps in Germany that leverage QR code for Presence Tracing
| `<URL>` | The URL associated with the respective contact tracing apps, with or without a partial path. |
| `<VENDOR_DATA>` | Any vendor-specific data such as the venue id in the vendor's system. This data may be passed to the vendor-specific app upon interaction by the user if a deeper integration is required. |
| `[VENDOR_ADDITIONAL_DATA]` | Additional vendor-specific data (optional). |
| `<ENCODED_PAYLOAD>` | A representation of the Protocol Buffer message `QRCodePayload` encoded in base64. Note that the signature must have been created by the CWA Server. |
| `<ENCODED_PAYLOAD>` | A representation of the Protocol Buffer message `QRCodePayload` encoded in base64url. |
**Note:** Any contact tracing apps that integrate with CWA must ensure that they do not process any information from the CWA part of the QR code.