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 19a3bb5
Browse filesBrowse the repository at this point in the historyBrowse files
-resume took no other arguments, so a scan stopped by a throttling
resolver or a spent time budget could only continue at the same rate,
timeout and budget.
-resume now accepts the pacing flags (-rate, -rate-per-resolver, -t,
-timeout, -attempts, -auto-rate, -no-abort, -max-duration) after the
state file and applies them over the saved arguments; any other flag is
still refused. The next state file records the new values, and a
changed SUBENUM_* or config value for a pacing flag no longer blocks a
resume.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Fixes#309
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
@@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
8
8
## [Unreleased]
9
9
10
10
### Added
11
+
-`-resume` accepts the pacing flags `-rate`, `-rate-per-resolver`, `-t`, `-timeout`, `-attempts`, `-auto-rate`, `-no-abort` and `-max-duration` next to the state file, so a scan stopped because timeouts piled up can continue at a gentler rate instead of the one that caused them. They apply over the saved command line, a changed value of one is no longer a reason to refuse the resume, and the next state file records them. Flags that change the candidates or the wildcard check stay refused (#309).
11
12
- Library: a `KindError` event has `Fatal` set when it ends the scan (the reliability guard's warning under `NoAbort` is the one error without it), and `KindDone` has `Failed` set when the scan failed. The CLI, the TUI, `Scan` and `subenum mcp` now read these instead of each working it out from the errors seen and the no-abort setting; exit codes, `Scan` errors and verdicts are unchanged (#308).
12
13
- The TUI configuration form includes **Sources** and **Permute** fields for `-sources` and `-permute`. The passive sources named in Sources (`ct`, `wayback`) are asked while the wordlist loads and their names are scanned with the wordlist's; a source that fails is a warning on the scan screen, and none is asked with Simulate on. With Permute on, a permutation pass follows the scan on the same screen, and the finished screen's verdict and counters cover both passes. With either field set, the results file names what proposed each result (`sources`, and `permutation` for a permutation hit) and its summary has the `sources` and `permutation` entries the CLI's report has (#274).
13
14
- Each result says what proposed it: a `sources` list in JSON and JSONL and a last `sources` column in CSV (joined with `;`), holding `wordlist`, `ct`, `wayback` and `axfr`, every one that had the name, or `permute` alone for a `-permute` hit. A name found by `-recursive` below another is the wordlist's. The run-quality report counts the results each passive source had proposed (`found` in its `sources` entry) and a zone transfer's (`axfr_found`). Text output, the TUI's files and `subenum mcp` reports are unchanged (#273).
Copy file name to clipboardExpand all lines: README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -307,7 +307,7 @@ This table describes `main`, which can be ahead of the latest release: a release
307
307
|`-dry-run`|`false`| Print the plan without scanning: candidates after dedupe and `-exclude`, query and duration estimates, and the resolver preflight (its only DNS query), then exit; JSON with `-format json` or `jsonl`|
308
308
|`-version`| n/a | Print version and exit |
309
309
|`-retries <n>`| n/a |**Deprecated** - alias for `-attempts`, prints a warning |
310
-
|`-resume <file>`| n/a | Resume a run that was interrupted, ran out of `-max-duration` or was aborted, from its state file; takes no other arguments |
310
+
|`-resume <file>`| n/a | Resume a run that was interrupted, ran out of `-max-duration` or was aborted, from its state file; takes no other arguments but the pacing flags (`-rate`, `-t`, `-timeout`, ...) |
|`-state <file>`|`subenum-resume.json`| Where a run that was interrupted, ran out of `-max-duration` or was aborted saves its state for `-resume`|
313
313
@@ -380,6 +380,8 @@ Press `Ctrl+C` at any time to abort. In-flight queries drain, partial results ar
380
380
subenum -resume subenum-resume.json
381
381
```
382
382
383
+
The only flags `-resume` accepts next to the state file are the pacing flags `-attempts`, `-auto-rate`, `-max-duration`, `-no-abort`, `-rate`, `-rate-per-resolver`, `-t` and `-timeout`: for example `subenum -resume subenum-resume.json -rate 20 -auto-rate` continues a scan that timeouts slowed down at a gentler rate. They apply over the saved command line and are recorded in the next state file. Flags that change which names are queried or how wildcards are detected (`-w`, `-type`, `-dns-server`, `-depth` and the rest) cannot change on a resume.
384
+
383
385
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.
Copy file name to clipboardExpand all lines: docs/_includes/flags.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
@@ -30,7 +30,7 @@
30
30
|`-rate <int>`| - | Max DNS queries per second on the wire, all workers combined; counts every record type, retry and wildcard probe (0 = unlimited) |
31
31
|`-rate-per-resolver <int>` {% include unreleased.html flag="rate-per-resolver" %} | - | With -r, max DNS queries per second sent to each pool resolver; -rate still caps the total (0 = unlimited) |
32
32
|`-recursive`| - | Recursively enumerate subdomains of discovered subdomains |
33
-
|`-resume <string>`| - | Resume a run that was interrupted, ran out of -max-duration or was aborted, from its state file (no other arguments) |
33
+
|`-resume <string>`| - | Resume a run that was interrupted, ran out of -max-duration or was aborted, from its state file (no other arguments but the pacing flags -rate, -rate-per-resolver, -t, -timeout, -attempts, -auto-rate, -no-abort and -max-duration) |
34
34
|`-retries <int>`| - | Deprecated: use -attempts instead |
35
35
|`-retry-inconclusive` {% include unreleased.html flag="retry-inconclusive" %} | - | After each scan, look up once more (against -dns-server) every name that timed out, was refused or failed; names it resolves are reported, but not expanded by -recursive |
36
36
|`-sarif <string>`| - | Write takeover candidates to this file as SARIF 2.1.0, for GitHub code scanning (needs CNAME or NS in -type) |
fs.BoolVar(&f.ct, "ct", false, "Add names from Certificate Transparency logs (crt.sh, one HTTPS request per target, no API key) as candidates and -permute seeds")
fs.StringVar(&f.stateFile, "state", defaultStateFile, "Where a run that was interrupted, ran out of -max-duration or was aborted saves its state for -resume")
261
-
fs.String("resume", "", "Resume a run that was interrupted, ran out of -max-duration or was aborted, from its state file (no other arguments)")
261
+
fs.String("resume", "", "Resume a run that was interrupted, ran out of -max-duration or was aborted, from its state file (no other arguments but the pacing flags -rate, -rate-per-resolver, -t, -timeout, -attempts, -auto-rate, -no-abort and -max-duration)")
262
262
fs.StringVar(&f.diff, "diff", "", "Previous results file (any -format); report only names added or removed since then, and exit 4 when there are changes")
263
263
fs.BoolVar(&f.diffRecords, "diff-records", false, "With -diff, also report names whose records changed (a re-pointed CNAME, moved addresses), compared over the -type record types; needs a json, jsonl or csv -diff file")
264
264
fs.StringVar(&f.resolvers, "r", "", "File of resolvers (ip or ip:port, one per line) to spread queries over; every hit is re-validated against -dns-server")
0 commit comments