Skip to content

webtransport: use CBOR to encode cert hashes during Noise handshake #429

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

Closed
marten-seemann wants to merge 1 commit into from
Closed

webtransport: use CBOR to encode cert hashes during Noise handshake #429

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
10 changes: 4 additions & 6 deletions webtransport/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,10 @@ The first stream that the client opens on a new WebTransport session is used to
In order to verify that the end-to-end encryption of the connection, the peers need to establish that no MITM intercepted the connection. To do so, the client MUST include the certificate hash that was used to establish the connection as payload of the first Noise message (the `e` message). This payload is not encrypted, but the Noise handshake provides integrity protection.
If the client was willing to accept multiple certificate hashes, but cannot determine which certificate was actually used to establish the connection (this will commonly be the case for browser clients), it MUST include a list of all certificate hashes.

Certificate hashes are encoded using the following protobuf message:
```proto
syntax = "proto2";

message WebTransport {
repeated bytes cert_hashes = 1;
Certificate hashes are sent in this CBOR-encoding message:
```cbor
{
"webtransport-hashes" []byte string
}
```

Expand Down