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

Mention forward secrecy #25

merged 2 commits into from
Oct 19, 2024

Conversation

tfpauly
Copy link
Collaborator

@tfpauly tfpauly commented Oct 15, 2024

Closes #23

Make it more explicit that we inherit the security considerations of normal OHTTP

Closes #23 

Make it more explicit that we inherit the security considerations of normal OHTTP
@tfpauly tfpauly self-assigned this Oct 15, 2024
Copy link
Collaborator

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where I start to agree with those who express concerns about this design. If a message can be replayed, then how that is replayed might be exploited by a malicious relay to effect change.

Maybe we need to do a little more analysis on that aspect of this. A section on interactivity and replay might help expound on those risks.

draft-ietf-ohai-chunked-ohttp.md Outdated Show resolved Hide resolved
@tfpauly tfpauly merged commit 0f1d398 into main Oct 19, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add warning about perfect forward secrey
2 participants