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 96a04d5
Browse filesBrowse the repository at this point in the historyBrowse files
Don't spend -max-duration on pre-scan probes (#340)
scan.Run now moves the deadline forward by the time the resolver
preflight and wildcard probes took, as long as the budget had not run
out before the scan started (a later -dL target keeps a spent budget).
Under a low -rate those probes could take all of a short budget, so a
run tested no names and every -resume probed again without progress.
The time-budget notice says when the budget ran out before any name was
tested. TestE2EMaxDuration now requires names tested, and a -resume
that skips fewer names than the first run.
Fixes#340
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
@@ -67,6 +67,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
67
67
- Less memory on large wordlists and busy scans: `-sources`, `-ct`, `-axfr` and `-permute` check their names against the wordlist without building a set as large as it (about 200 MB per feature and target on a 5M-line list), a `-simulate-zone` lab scan no longer keeps a count per queried name (about 170 MB on a 1M-line list), and a `CNAME` lookup reads a UDP answer into a buffer sized for the 1232-byte EDNS payload it advertises instead of 64 KB. Results are unchanged (#321).
68
68
69
69
### Fixed
70
+
- The resolver preflight and wildcard probes made before a target's first name no longer use up `-max-duration`. Under a low `-rate` they could take all of a short budget, so the run tested no names and each `-resume` probed again and made no progress. A budget that runs out before any name was tested now says so (#340).
70
71
- Release archives and the container image carry the licence notices of the Go standard library and every module linked into the binary, in a `THIRD_PARTY_LICENSES` file generated at release time by `tools/licenses` from the module cache. The image also carries the project's `LICENSE`; both are in `/usr/share/doc/subenum/` (#326).
71
72
- With `-format csv`, each row reaches stdout as its result is found, as with the other formats, instead of when 4 KB had built up or the run ended; a pipe sees live rows and a force quit loses none (#319).
72
73
- With both `-max-queries` and `-max-duration`, a deadline that fires after the query cap no longer loses the chunk of names admitted but not yet handed out: they count as skipped, so tested plus skipped adds up to every candidate and progress reaches 100%, and the run is marked as stopped by the time budget. Children of a name found after a budget stop whose whole branch is excluded count as excluded, not skipped, so they cannot make a complete scan look incomplete (#317).
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -273,7 +273,7 @@ This table describes `main`, which can be ahead of the latest release: a release
273
273
|`-no-abort`|`false`| Keep scanning after the 20% resolver failure-rate abort (warning is still emitted) |
274
274
|`-auto-rate`|`false`| When more than 20% of the last 200 lookups failed, halve the query rate (from the rate reached so far when `-rate` is 0) and keep going, with a `rate` notice; speed back up by a quarter at a time, to the rate it started from, once a window of lookups is healthy. Only after 6 back-offs, or at 5 queries/s, does the reliability guard abort. The report counts `rate_backoffs` and the `final_rate`. Pairs well with `-retry-inconclusive`, which retries the names that failed while the resolver was overloaded |
275
275
|`-max-queries <n>`|`0`| Max candidate names to test (0 = unlimited). Each name sends one query per record type per attempt |
276
-
|`-max-duration <d>`|`0`| Time budget for the whole run, e.g. `20m` (0 = unlimited). Then no new names are tested, lookups already under way finish, and the run ends normally with its results, report (`stopped_by: "duration"`) and a `degraded` verdict, and saves a `-state` file so `-resume` tests the rest. Under `-dL` it covers all targets |
276
+
|`-max-duration <d>`|`0`| Time budget for the whole run, e.g. `20m` (0 = unlimited). Then no new names are tested, lookups already under way finish, and the run ends normally with its results, report (`stopped_by: "duration"`) and a `degraded` verdict, and saves a `-state` file so `-resume` tests the rest. Under `-dL` it covers all targets. The resolver preflight and wildcard probes made before a target's first name are not counted|
277
277
|`-retry-inconclusive`|`false`| After each scan, look up once more (against `-dns-server`, never the `-r` pool) every name that timed out, was refused or failed. An answer replaces the first outcome in the counts; a name that resolves is reported, but not expanded by `-recursive`. Skipped after an abort, an interrupt or once `-max-duration` runs out. The report counts `retried` and `recovered`|
278
278
|`-inconclusive <file>`| n/a | Write the names still without an answer (timeout, refused, other) to this file, one per line, sorted, so a later run can retry them with `-w <file>`|
279
279
|`-o <file>`| n/a | Write results to file in addition to stdout; repeat for several files, each in `-format` or in the format named as a prefix (`-o names.txt -o jsonl:results.jsonl`) |
0 commit comments