Closed blightzero closed 3 months ago
Thanks! We're looking into a more elegant solution to this problem that wont cause any data loss. Will keep you updated.
I added logic to make sure the information is available on the SSL::Info at time of logging to connection state remove in https://github.com/FoxIO-LLC/ja4/pull/88
Merged #88 which solves this issue as well. Thanks for bringing it to our attention!!
When JA4 and JA4s scripts respectively were run they would sometimes create exceptions like this:
JA4s:
JA4:
This patch first checks if the connection ID exists and then does the lookup, thus avoiding the exception output.