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 c5e4454
Browse filesBrowse the repository at this point in the historyBrowse files
Let config and SUBENUM_* set several -w or -o files (#353)
-w and -o are repeatable on the command line, but the config file
rejected a JSON array for them and a string became one path with commas
in it. The config file now takes an array for w and o (each entry is one
value, set in order, commas kept) and for sources, as it already did for
exclude and type. To match the other list settings, a w or o string in
the config file or SUBENUM_W/SUBENUM_O is a comma-separated list; a path
with a comma goes in an array entry or on the command line.
-print-config shows w and o as a JSON array so ["a,b"] and ["a","b"]
are told apart.
Fixes#353
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
@@ -70,6 +70,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
70
70
- 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).
71
71
72
72
### Fixed
73
+
- The config file and `SUBENUM_W`/`SUBENUM_O` can set several `-w` wordlists or `-o` files, as the command line can. The config file takes a JSON array for `w` and `o`, one file per entry (`"o": ["names.txt", "jsonl:results.jsonl"]`), and for `sources`, as it already did for `exclude` and `type`; a string for `w` or `o` there or in the environment is a comma-separated list, as it is for the other list settings, where it used to become one path with commas in it. `-print-config` shows `w` and `o` as a JSON array, so one file whose name has a comma is told apart from two (#353).
73
74
- A name whose lookup of one requested type timed out, was refused or failed while another type answered is no longer a plain found result with the records that came back. The whole lookup is tried again up to `-attempts`, and when the failed type never answers the result is marked partial: a `partial` field in JSON and JSONL, `PARTIAL` in text with `-show-records`, a `partial answers` line in the breakdown, and `Stats.Partial` in the library. Partial answers lower the run's verdict as failed lookups do (degraded at 1%), and `-diff-records` does not report a partial name as changed, since its missing records may only be a lookup that failed (#357).
74
75
- 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).
75
76
- 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).
- The config file is `config.json` in your user config directory (`~/.config/subenum/` on Linux, `~/Library/Application Support/subenum/` on macOS, `%AppData%\subenum\` on Windows), or the path in `SUBENUM_CONFIG`. Keys are flag names; values are strings, numbers or booleans, and `exclude`and `type` also take a list of strings.
316
+
- The config file is `config.json` in your user config directory (`~/.config/subenum/` on Linux, `~/Library/Application Support/subenum/` on macOS, `%AppData%\subenum\` on Windows), or the path in `SUBENUM_CONFIG`. Keys are flag names; values are strings, numbers or booleans, and `exclude`, `type`and `sources` also take a list of strings. The repeatable `w` and `o` take a list too, one file per entry (`"o": ["names.txt", "jsonl:results.jsonl"]`); a string for them, in the config file or in `SUBENUM_W`/`SUBENUM_O`, is a comma-separated list, so name a file whose path has a comma in a list entry or on the command line.
317
317
- Each flag also reads `SUBENUM_<FLAG>`, upper-cased with dashes as underscores: `SUBENUM_DNS_SERVER`, `SUBENUM_RATE`, `SUBENUM_T`. Mode flags (`tui`, `version`, `print-config`, `dry-run`, `resume`) are command-line only.
318
318
- The TUI (`-tui`) starts its form from these values too, and from flags and the domain given with `-tui` on the command line, over the values it remembers from its last session.
319
319
-`subenum -print-config` shows every effective setting and where it came from (`flag`, `env`, `config` or `default`). It, `-h` and `-version` still work when a value is bad, so you can find it; a scan refuses to start and names every bad value.
Copy file name to clipboardExpand all lines: docs/cli.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
@@ -44,7 +44,7 @@ Flags may appear before or after the domain. The domain is normalized to its hos
44
44
Settings you repeat on every run can live in the environment or a config file. They apply to scans (and `-tui`), not to the `mcp` subcommand, which takes its settings from its own flags only. Precedence, highest first: **command-line flag, then `SUBENUM_*` environment variable, then config file, then built-in default.**
45
45
46
46
- Each flag reads `SUBENUM_<FLAG>`, upper-cased with dashes as underscores: `SUBENUM_DNS_SERVER`, `SUBENUM_RATE`, `SUBENUM_T`.
47
-
- The config file is `config.json` in your user config directory (`~/.config/subenum/` on Linux, `~/Library/Application Support/subenum/` on macOS, `%AppData%\subenum\` on Windows), or the path in `SUBENUM_CONFIG`. Keys are flag names; values are strings, numbers or booleans, and `exclude`and `type` also take a list of strings. Mode flags (`tui`, `version`, `print-config`, `dry-run`, `resume`) are command-line only.
47
+
- The config file is `config.json` in your user config directory (`~/.config/subenum/` on Linux, `~/Library/Application Support/subenum/` on macOS, `%AppData%\subenum\` on Windows), or the path in `SUBENUM_CONFIG`. Keys are flag names; values are strings, numbers or booleans, and `exclude`, `type`and `sources` also take a list of strings. The repeatable `w` and `o` take a list too, one file per entry (`"o": ["names.txt", "jsonl:results.jsonl"]`); a string for them, in the config file or in `SUBENUM_W`/`SUBENUM_O`, is a comma-separated list, so name a file whose path has a comma in a list entry or on the command line. Mode flags (`tui`, `version`, `print-config`, `dry-run`, `resume`) are command-line only.
48
48
- The TUI (`-tui`) starts its form from these values too, and from flags and the domain given with `-tui` on the command line, over the values it remembers from its last session.
49
49
-`subenum -print-config` prints every effective setting and where it came from: `flag`, `env`, `config` or `default`. With a bad value, `-h`, `-version` and `-print-config` still run and warn; a scan refuses to start and names every bad value.
50
50
- When `-attempts` and the deprecated `-retries` both have a value, the one from the higher-precedence source wins; both on the command line (or both from the same file) is an error.
0 commit comments