Adding support of SSHKEYLOGFILE #566
Open
+338
−9
Conversation
This file contains hidden or 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
When SSHKEYLOGFILE is set, shared secrets used in key exchange (e.g., during initial or rekey events) are logged alongside the KEXINIT cookie. This supports offline decryption tools like Wireshark for debugging and protocol analysis. WARNING: Do not enable in production environments. This exposes session secrets.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Log SSH shared secret for external protocol analysis via SSHKEYLOGFILE
When SSHKEYLOGFILE is set, shared secrets used in key exchange (e.g., during
initial or rekey events) are logged alongside the KEXINIT cookie. This supports
offline decryption tools like Wireshark / Tshark for debugging and protocol analysis.
See README.keylog for details
WARNING: This exposes session secrets on client side.