ARCHITECTURE.md names missing identifiers and describes replaced behavior
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 85/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- go
- Área
- documentation
Línea de trabajo
Empieza con docs/ARCHITECTURE.md y comprueba cada línea citada contra el código al que se refiere: main_wordlist.go (prepareWordlist), main.go (validateArgs, alrededor de las líneas 211 y 283-301), internal/dns/resolver.go, internal/dns/cname.go, internal/output/writer.go (writeJSONElement), internal/validate/validate.go, internal/scan/runner.go, main_ct.go y main_config.go. Corrige los identificadores obsoletos, el requisito de -w, la afirmación sobre el búfer de JSON, las formas de los servidores DNS, el comportamiento de EventDone y la entrada de -dry-run. Se considera terminado cuando cada elemento de la lista de verificación del issue está corregido y la lista de archivos incluye cname.go.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Ten statements in docs/ARCHITECTURE.md contradict the code: two function names that no longer exist, -w described as required, JSON output described as buffered, and a scan described as able to end without EventDone.
Where
docs/ARCHITECTURE.md:66docs/ARCHITECTURE.md:124docs/ARCHITECTURE.md:158docs/ARCHITECTURE.md:194docs/ARCHITECTURE.md:197docs/ARCHITECTURE.md:250docs/ARCHITECTURE.md:253docs/ARCHITECTURE.md:268docs/ARCHITECTURE.md:331docs/ARCHITECTURE.md:343main_wordlist.go:56main.go:211main.go:283-301internal/dns/resolver.go:284-290internal/dns/resolver.go:329-332internal/dns/cname.go:49-62internal/output/writer.go:255internal/validate/validate.go:47-67internal/scan/runner.go:590-596main_ct.go:28main_config.go:39
Details
Each item below contradicts the code at d0c56f0:
- :66
main_wordlist.go - readWordlist. NoreadWordlistexists; the file definesprepareWordlist(main_wordlist.go:56) and thewordlistPathsflag value. - :124 "
validateFlags, which checks that-wand a target are present", and :250 "When-wor a target ... is missing ... exits with status 2".-wis optional (main.go:211, "omitted: the bundled top-5000 list");validateArgschecks only the domain or-dL(main.go:283-301). - :158 "one lookup per requested record type (... CNAME via
LookupCNAME...)". CNAME goes through the package's ownlookupCNAME, one query (cname.go:49-62; resolver.go:286 "not Go's LookupCNAME, which also sends A and AAAA (#249)"), and the types are looked up at the same time (resolver.go:329-332, #250). Line 160 of the same document already says the opposite about CNAME. - :194 "In
jsonformat results are buffered and written as a single array byFinish" and :197 "Finish- writes the buffered JSON array". The array is streamed element by element (writeJSONElement, writer.go:255, #181; CHANGELOG.md:47). - :253 "The DNS server must be a valid
ip:portwith an IP host".tls://host[:port]andhttps://host/pathare accepted, and their host may be a name (validate.go:47-67). Line 125 of the same document says so. - :268 "a failed preflight or an inconclusive wildcard check ... emits
EventErrorand ends the scan withoutEventDone". Every scan ends with exactly oneEventDone, withStoppedset when it ended before the candidates (runner.go:590-596, #99). - :331 "
withCTEntriesappends those not already in the wordlist". No such function; the passive names are gathered bypassiveNames(main_ct.go:28) and merged bypassive.Merge. - :343 lists the flags never taken from defaults as
-tui,-version,-print-config,-resume,-h;dry-runis innoDefaultFlagstoo (main_config.go:39), as README.md:417 and docs/cli.md:44 say. - The file list (:75-84) has no entry for
internal/dns/cname.go.
Impact
A contributor searching for readWordlist or withCTEntries finds nothing, and one who writes a scan.Run consumer from section 4.3 will treat a missing EventDone as a possible outcome, or budget five queries for -type A,AAAA,CNAME instead of three.
Suggested fix
Correct the nine items in place: rename the two functions, drop "-w and" from 2.1 and 4.1, rewrite the Lookups bullet (own lookupCNAME, concurrent types), say JSON is streamed and Finish closes the array, list the three resolver forms in 4.1, say EventDone follows with Stopped set in 4.3, add -dry-run to 5.8 and cname.go to the file list.
Acceptance criteria
- Each checklist item under Details is corrected
Getting started
- Relevant files:
docs/ARCHITECTURE.md,main_wordlist.go,main.go,internal/dns/resolver.go - How to run tests:
make test(orgo test ./...). Tests must stay hermetic: use-simulate,-simulate-zoneor the local DNS test server, never a live domain. - Related docs:
docs/DEVELOPER_GUIDE.md,docs/ARCHITECTURE.md
Filed by repo-audit/full-audit at d0c56f0. Severity: low. Effort: S. audit-key: documentation|docs/ARCHITECTURE.md|stale-identifiers
- Lenguaje dominante
- Go
- Estrellas
- 1
- Forks
- 1
- Merge medio
- 6 h 42 min
- PR fusionados (30 d)
- 7
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TMHSDigital/subenum
-
good first issue severity: low tech-debt
Dificultad 2/5 Medio día Aptitud para principiantes 75/100
TMHSDigital/subenum#329 ·
Los mantenedores suelen responder en 1 día
-
area: release dependencies good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
TMHSDigital/subenum#324 ·
Los mantenedores suelen responder en 1 día
-
ci good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
TMHSDigital/subenum#323 ·
Los mantenedores suelen responder en 1 día
-
area: output bug good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
TMHSDigital/subenum#319 ·
Los mantenedores suelen responder en 1 día
-
community documentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
TMHSDigital/subenum#135 ·
Los mantenedores suelen responder en 1 día
Todos los issues de TMHSDigital/subenum
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
GillMacedo/godebugdiff#13 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
GillMacedo/racesift#14 ·
-
IsTextFile reads the whole file into memory (OOM on large files in the file watcher)Posiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
gtsteffaniak/filebrowser#3395 ·
Los mantenedores suelen responder en 1 día
-
effort:s impact:low raised-by:worker risk:low
Dificultad 1/5 Menos de una hora Aptitud para principiantes 70/100
medici-finance/assay#6496 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
kind/bug require/reproduce require/severity
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día