Add strict kex #104
Closed
Add strict kex #104
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
|
Similar to The |
|
See #105 that correctly documents this in |
This pull request was closed.
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.
This PR adds both client and server extensions to the specification page and all implementations that support these extensions.
I added both client and server extensions separately, even though I could not find an implementation that includes either one. So either both are supported, or none.
I did not list implementations with support in unreleased versions, such as Dropbear and libssh2.
The information about support is gathered primarily from the liste patches on the Terrapin website. I added a couple of other implementations based on the changelog referenced from the existing spec file.
Finally I noticed that some implementations did not contain an extensions variable in the spec file. As a result a couple of implementations now list several other extensions as 'no/unsupported'. Note that I did not check support for other extensions, so please let me know if this is an issue.
This closes #103