-
Notifications
You must be signed in to change notification settings - Fork 251
Fix handling of multi-message TSIG responses #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #300 +/- ##
============================================
+ Coverage 64.18% 65.53% +1.34%
- Complexity 2765 2834 +69
============================================
Files 178 184 +6
Lines 12546 12724 +178
Branches 1915 1944 +29
============================================
+ Hits 8053 8339 +286
+ Misses 4002 3876 -126
- Partials 491 509 +18
☔ View full report in Codecov by Sentry. |
I'm afraid its not quite right. In this case, there is still a bug with verify process (and a symmetric bug with the generate process). The signature of the TSIG record isn't being added at quite the right time (as usual only in the case of mixed signed/unsigned messages). On the bright side, the bug is much more narrow at this point. I've got a branch of 'tsig-stream' I'll submit shortly as another PR. |
Co-authored-by: Frank Hill <frank@arin.net>
Kudos, SonarCloud Quality Gate passed! |
Closes #295
Closes #297
Closes #298
Closes #299
Closes #301