/settings.rst
/yamlsettings.rst
/rec-metrics-gen.rst
+http-api/recursor-generated-schema.yaml
help: .venv
@$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
-.PHONY: help Makefile.sphinx
+.PHONY: help Makefile.sphinx generate-jsonschema.py http-api/authoritative-api-swagger.yaml
+
+http-api/recursor-generated-schema.yaml: .venv generate-jsonschema.py http-api/authoritative-api-swagger.yaml
+ .venv/bin/python ./generate-jsonschema.py http-api/authoritative-api-swagger.yaml $@
# Catch-all target: route all unknown targets to Sphinx using the new
# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS).
-%: Makefile.sphinx .venv
+%: Makefile.sphinx .venv http-api/recursor-generated-schema.yaml
@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)
.venv:
# -- Options for the Sphinx-Immaterial JSON Domain ------------------------
json_schemas = [
- "http-api/authoritative-api-swagger.yaml",
"http-api/recursor-schema.yaml",
+ "http-api/recursor-generated-schema.yaml",
]
# -- Options for HTML output ----------------------------------------------
--- /dev/null
+../../../docs/generate-jsonschema.py
\ No newline at end of file
- Risk of system compromise: No
- Solution: Upgrade to PowerDNS Recursor 3.6.1
- Workaround: Restrict service using
- |allow-from|_, install
+ :ref:`setting-allow-from`, install
script that restarts PowerDNS
-.. |allow-from| replace:: ``allow-from``
-.. _allow-from: :ref:`setting-allow-from`
-
Recently, we've discovered that PowerDNS Recursor 3.6.0 (but NOT
earlier) can crash when exposed to a specific sequence of malformed
packets. This sequence happened spontaneously with one of our largest