define how private networks work with QUIC v1 #250
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Otherwise, for short packets we'd only encrypt the AEAD tag. An attacker could then still unprotect the packet, and ignore the incorrect tag.
|
@marten-seemann what is the current status of this pull request? Is this awaiting review? |
|
We just closed the implementation of this libp2p/go-libp2p-quic-transport#119. |
|
Thanks @marten-seemann. With your reply in mind I am assuming that there is no intention to merge this pull request, thus I am closing it. Feel free to re-open in case I am missing something. This could still act as a reference in case we get around to implementing RFC 8773. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.