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
{{ message }}
Repository navigation
Commit 43a6627
Browse filesBrowse the repository at this point in the historyBrowse files
Refuse resolver dials under a finished context (#295)
Go runs A and AAAA lookups in a goroutine that keeps retrying after the
caller's timeout, under a cancelled context that has lost the caller's
values. With pooled sockets such a retry reached the wire outside -rate
and the query count. The Dial hook now returns the context's error
before counting, pacing or dialing, for UDP, TCP, DoT and DoH alike.
Co-Authored-By: Claude Mythos 5.2 <noreply@anthropic.com>
Fixes#295
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,6 +62,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
62
62
- Shell completion for `-type` offers `NS`, `MX` and `TXT`, which `-type` has accepted since #194. The record types and output formats now come from one list each, which completion, the MCP schema and flag checking share (#264).
63
63
- When `-max-queries` or `-max-duration` stops a scan, candidates `-exclude` would have kept out are counted as `excluded`, not skipped, so a budget that ran out only past excluded names leaves the verdict `complete` (and `-diff` reporting removals) instead of `degraded` (#238).
64
64
-`-resume` no longer skips names when a passive source failed in the interrupted run and works on resume. The failed source was fetched again, its names were inserted before later sources' names, and the saved position then pointed past candidates that were never tested while the verdict could still read `complete`. The resume state now records a failed source with no names, and the resumed run replays that (#237).
65
+
- An A or AAAA lookup that timed out no longer sends the same name again in the background. The repeats went out about five seconds apart on a reused socket, outside `-rate` and `-rate-per-resolver`, uncounted in the query total, and could continue after the scan had ended; a lookup whose time is up now gets no connection (#295).
65
66
66
67
### Security
67
68
-`go.mod` names a patched toolchain (`toolchain go1.26.11`) beside the unchanged `go 1.26.0` floor, so `go install` and the action's `version: source` build with the security-fixed `net/http`, `crypto/tls` and `crypto/x509` instead of the original 1.26.0 standard library; with the default `GOTOOLCHAIN=auto` an older local Go fetches it. Release binaries were already built with a current Go (#243).
0 commit comments