Conversation
It is intentional that this commit does not compile. In order to effectively track changes made from the vendor's code, this is a direct import without fixes for the ZGrab xssh package requirements. Future commits will fix and restore functionality. Code is directly imported from breml/crypto@09c4372
… groups, are checked.
|
What's the license and copyright situation with this code? |
|
The repo is a fork of the golang/crypto repo with with the exact same license. https://github.com/breml/crypto/blob/master/LICENSE |
|
It looks like this is going to conflict with #215 |
|
Depending on how good the merging is, the flag.go file may conflict. If it does, it will be superficial and can be manually merged with little effort. |
|
Hi there, I am the author of the mentioned code for DH GEX. I just wanted to add some notes.
|
|
@breml thank you for the additional information. I greatly appreciate you reaching out and providing context. @aaspring given @breml's comments, are there any changes that you want to make to this PR or is it still good to go? Offhand it looks fine to me, but given that @breml mentions a drop in version, I wanted to double check that this is still the right approach. @dadrian Can you please take a once over on this code when you have a moment? I think you're the other person on the ZGrab team most familiar with SSH protocol. |
|
I will look into the drop-in version today and see. A self-contained approach would be better given that it may be added to the upstream package which would warrant us removing this patch and using the upstream version. @breml Thank you very much for dropping in and letting us know there's a better approach. |
|
@aaspring ping me when you want review |
|
Closing PR. GEX functionality is being added via @breml's drop-in implementation in PR 232. |
Add the
diffie-hellman-group-exchange-sha1DH KEX to the xssh scanner. This is based on the implementation by @breml with additions for customization and JSON output.Example output --
The sub-grouped parameters and broken out signature fields will be added via their appropriate issues' commit.
@breml's original implementation: breml/crypto@09c4372