norrisjeremy
commented
2 months ago kex-strict-c-v00@openssh.com & kex-strict-s-v00@openssh.com shouldn't be placed under extension but rather kex.
Similar to ext-info-c & ext-info-s, they are advertised by both client & server side along side kex algorithms.
The extension section is intended to document SSH_MSG_EXT_INFO extensions (see RFC-8308).
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