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 1bddf7d
Browse filesBrowse the repository at this point in the historyBrowse files
Skip a finished main pass when resuming a -permute pass (#358)
A target stopped in its -permute pass was saved as not done, so the
resumed run scanned its main pass again from the end. Under -recursive
that re-expanded every saved parent, and a name the repeat found anew
changed the permutation candidate list the saved position indexes.
The resume state now records main_done for such a target; the resumed
run takes the saved main pass as its final event, as it does for a
finished target, and goes straight to the permutation pass with the
saved names as its seeds. The saved main pass is kept whole, without
the repeat discount a re-scanned pass gets.
Fixes#358
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
@@ -68,6 +68,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
68
68
- 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).
69
69
70
70
### Fixed
71
+
- Resuming a scan stopped in its `-permute` pass (Ctrl+C or `-max-duration`) no longer scans the finished main pass again. Under `-recursive` that repeated every lookup below the saved names, and a name the repeat found anew changed the permutation candidate list, so the resumed pass started at the wrong place in a different list, skipping some candidates and testing others twice. The resume state now records that the main pass finished, and the resumed run goes straight to the permutation pass with the saved names as its seeds (#358).
71
72
- When `-max-queries` or `-max-duration` stops a scan whose wordlist holds multi-label entries (such as `dev.api`), the untested names are counted as they would have been: ones `-exclude` would remove count as excluded rather than skipped, so a run whose only untested names were out of scope stays complete, and under `-recursive` a name the rest of the scan would have reached through two parents is counted as skipped once, so tested, skipped and excluded add up to the candidate total (#361).
72
73
- A CNAME target or name server that exists but has no A or AAAA record (NODATA, such as a name with only MX or TXT records) is no longer marked `dangling` or `dangling-ns`: Go reports it as not-found like a name that does not exist, so a target whose address lookup comes back empty now gets one more A query, and only an NXDOMAIN answer marks it. A probe that times out or fails marks nothing (#362).
73
74
- A wordlist entry that already ends in the target, such as a full name pasted from another tool, is scanned as the prefix in front of it: `www.example.com` under `example.com` is `www`, not `www.example.com.example.com`, and one that repeats an entry already in the list counts as a duplicate. The scan notes how many entries it shortened (#351).
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
@@ -408,7 +408,7 @@ The only flags `-resume` accepts next to the state file are the pacing flags `-a
408
408
409
409
<br>
410
410
411
-
The resumed run refuses to start if an input file, the wordlist (including the bundled one, which changes with the binary) or an effective setting (for example a `SUBENUM_*` variable or the config file) changed. It re-emits the earlier results (so `-o` and JSON output end up complete), skips targets that had finished, and continues the interrupted one from the first wordlist entry not yet fully looked up; a `-permute` pass resumes from its own position. At most about one worker pool's worth (`-t`) of lookups is repeated, and `-max-queries` covers the whole scan, so a resumed run only gets what is left of it. In recursive mode, names found before the interrupt have their children re-scanned. A resumed run that finishes deletes its state file. A run that `-max-duration` stopped with names untested, or that the reliability guard aborted, saves the same state (its exit code does not change), so `-resume` continues it too: a scheduled job with a time budget can work through a large wordlist over several runs. When `-diff` and `-o` name the same file, a run that saves a resume state leaves that file unchanged, so the resumed run compares against the same baseline and then writes the full results. Runs that read the wordlist or domain list from stdin cannot be resumed.
411
+
The resumed run refuses to start if an input file, the wordlist (including the bundled one, which changes with the binary) or an effective setting (for example a `SUBENUM_*` variable or the config file) changed. It re-emits the earlier results (so `-o` and JSON output end up complete), skips targets that had finished, and continues the interrupted one from the first wordlist entry not yet fully looked up; a `-permute` pass resumes from its own position. At most about one worker pool's worth (`-t`) of lookups is repeated, and `-max-queries` covers the whole scan, so a resumed run only gets what is left of it. In recursive mode, names found before the interrupt have their children re-scanned; a run stopped in its `-permute` pass resumes in that pass and does not scan the finished main pass again. A resumed run that finishes deletes its state file. A run that `-max-duration` stopped with names untested, or that the reliability guard aborted, saves the same state (its exit code does not change), so `-resume` continues it too: a scheduled job with a time budget can work through a large wordlist over several runs. When `-diff` and `-o` name the same file, a run that saves a resume state leaves that file unchanged, so the resumed run compares against the same baseline and then writes the full results. Runs that read the wordlist or domain list from stdin cannot be resumed.
0 commit comments