You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As reported by @bjoe2k4 on IRC (thanks), grepq() returns strange results for DNSCrypt-encrypted responses. It looks like the pointer we use to insert the DNS header into our response ring buffer points the DNSCrypt response, and not to the actual response from the backend anymore, meaning we would be reading the resolver magic and part of the nonce instead of the actual DNS header.
The text was updated successfully, but these errors were encountered: