Closed robinlandstrom closed 1 year ago
I am getting the same error running the self tests.
Thanks for spotting this - I suspect that the code path is only checked if the fuzz testing generates an invalid record which triggers the exception so I haven't seen this happen when I run run_tests.sh.
In the short term I've made a simple fix that just generates the right exception but haven't done any digging into the HTTPS record processing - the code was kindly donated by someone and I'm not familiar enough with the HTTPS record to work out what is happening (I've never come across one).
I've released 0.9.22 which includes the temporary fix (should be available on PyPi)
I will leave the issue open however and see if I get some time to look at the HTTPS records.
Took a look at this and found / fixed one issue in the parsing where the HTTPS parser ignores the length parameter. PR https://github.com/paulc/dnslib/pull/44
Merged - thanks (haven't released new version to PyPi yet - see next issue)
Hi Paul and thanks for a great library!
It seems like the change in dns.py https://github.com/paulc/dnslib/commit/ce070170f989a994fded1b973537e1fbb3a7c45c breaks the error reporting on parse errors on HTTPS records.
hexlify
return bytes andhex()
that was used earlier returns a string.Here is some code to reproduce, possibly there are some issues with the HTTPS parsing in general since this packet is parsed okay in Wireshark.
Anything I can do to help? Not that familiar with the HTTPS record type thou..