Doc updates to include additional ALPN extension values #277
+3
−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.
Overview
Adding examples to cover space character (
sp,0x20) handling in the ALPN Extension Value as we have seen some unexpected JA4 fingerprints in Wireshark when a space character is sent by the client.Please note, I have raised a an issue over on the Wireshark repo to highlight what we have seen: https://gitlab.com/wireshark/wireshark/-/issues/20966
Example 1
ALPN Extension Value sent by client:
ALPN Next Protocol: ' ' Hex values: 0x20Resulting JA4 Fingerprint (Note: double space in place of ALPN value)
Expected JA4 Fingerprint
Example 2
ALPN Extension Value sent by client:
ALPN Next Protocol: 'a ' Hex values: 0x61 0x20Resulting JA4 Fingerprint (Note: sinlge space set for second ALPN value)
Expected JA4 Fingerprint