Enabling SSLKEYLOGFILE Capability #19081
Open
+10
−0
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.
Purpose:
To enable SSLKEYLOGFILE capabilities as described in [1], [2]. This will enable diagnostic tools to inspect the contents of Chia's encrypted WebSocket messages, making it easier to debug or analyze Chia's networking protocol.
[1] https://www.ietf.org/archive/id/draft-ietf-tls-keylogfile-02.txt
[2] https://docs.python.org/3/library/ssl.html#ssl.SSLContext.keylog_filename
Current Behavior:
New Behavior:
By defining a keyfile path in any of the following environmental variables, TLS keys are written to that keyfile. Diagnostic tools like Wireshark can reference this keyfile and decrypt the network traffic.
CHIA_SSLKEYLOGFILENAME_SERVER
CHIA_SSLKEYLOGFILENAME_ROOT
CHIA_SSLKEYLOGFILENAME_CLIENT
Testing Notes: