Joe Testa

> For instance, the MAC policy prefers `[email protected]`, followed by the 512 variant. I made that decision for efficiency purposes. In my opinion, the 512-bit hash adds much more performance...

> At the very least, I think that ssh-audit scanning by policy should not fail if the administrator decided to put the stronger variant first. Just as long as all...

@keteague : it seems that all supported platforms issued patches to include the `[email protected]` key exchange marker. This marker signifies that the Terrapin vulnerability is fixed (that is, as long...

I suppose I'll mark this issue as complete, as no other replies have come after almost a week.

> To make -m available in PyPI, Snap and Docker builds, would you > continue with the existing approach for the Windows build, which is > when building a package,...

Implemented in 20fbb706b0a79478749a53ab1964ab18f6bb0a99. The next release will include the man page in the PyPI, Snap, and Docker builds.

The CVE code was written by the original author. I did make some additions to its database over time, but I haven't kept up with it... mainly for the same...

Yes, I do think this is something that can be tested. I just added the "help wanted" label to this issue, since it might be a while before I'll have...

My apologies for the late response. Your summary is accurate. The reason I added this logic was because OpenSSH has a special fall-back mechanism for GEX negotiation. It is hard-coded...

@thecliguy : Ping. We're about a month away from the next release, so I thought I'd see if you had any feedback on this issue. No rush, though.