Closed taida957789 closed 6 months ago
It seems to be a problem with gopacket processing none packets (e.g dhcp ack). You may use recover() to handling the panic when any panic was triggered in packet parser.
there is no any buffer size checking at DNSQuestion.decode function
Oops, I had no idea that gopacket would just panic on invalid packets like that. Perhaps the best solution would be to fix DNSQuestion.decode
ourselves with a fork and submit a PR?
Yes, I think so, but from the point of view of using the library, do we need to consider adding a fault-tolerance mechanism to the analyzer?
Turns out the latest version of gopacket already has this fix. I will just upgrade to the new version for now.