Skip to content
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.

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

Mention forward secrecy #25

Merged
merged 2 commits into from
Oct 19, 2024
Merged
Changes from 1 commit
Commits
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
8 changes: 8 additions & 0 deletions draft-ietf-ohai-chunked-ohttp.md
Original file line number Diff line number Diff line change
Expand Up @@ -289,6 +289,14 @@ Therefore, the response MUST NOT use `2^Nn` or more chunks.

# Security Considerations {#security}

In general, Chunked OHTTP inherits the same security considerations as Oblivious
HTTP {{OHTTP}}. Note specifically that while Chunked OHTTP allows for incremental
delivery and processing of messages, it does not add forward secrecy between
chunks. As with the non-chunked variant, forward secrecy is only provided when
changing the key configuration.
tfpauly marked this conversation as resolved.
Show resolved Hide resolved

## Message Truncation

The primary advantage of a chunked encoding is that chunked requests or responses can
be generated or processed incrementally. However, for a recipient in particular,
processing an incomplete message can have security consequences.
Expand Down
Loading