Closed daehee closed 3 years ago
@daehee Can you share the (redacted) tls-scan output?
@daehee I've made some code changes that is expected to fix this issue.
Please test new binary and confirm. https://github.com/prbinu/tls-scan/releases/tag/1.4.4
@prbinu just tested v1.4.4 and tripping on the same error. See output below:
The tls-scan output file is 456M, but I can email you snippets if it would be helpful.
Another jq parse error are invalid escape patterns \*
in the certificate values.
@daehee Please share the output snippets to prbinu@yahoo.com
@daehee I've fixed the issue. Please try the new binary: https://github.com/prbinu/tls-scan/releases/tag/1.4.5
@prbinu I just ran another mass scan with tls-scan v1.4.5, and confirming that this latest release did clear those issues reported above.
Another edge case discovered for: Invalid string: control characters from U+0000 through U+001F
This should fix the issue. I have escaped all control chars. https://github.com/prbinu/tls-scan/releases/tag/1.4.6
@prbinu closing the loop on this issue, this latest 1.4.6 release cleared all errors with jq parse of my sample output file.
@daehee thanks for confirming!
tls-scan outputs a malformed JSON line item, which throws errors when trying to parse the output file with jq.
jq error:
Line 14607 in tls-scan output file -- notice ending with
,
char and missingcertificateChain
key.