Make sure the documentation build works.

Makefile

@@ -14,6 +14,11 @@ irkerhook.1: irkerhook.xml
 irkerhook.html: irkerhook.xml
 	xmlto html-nochunks irkerhook.xml
 
+security.html: security.txt
+	asciidoc -o security.html security.txt
+hacking.html: hacking.txt
+	asciidoc -o hacking.html hacking.txt
+
 install: irkerd.8 irkerhook.1 uninstall
 	install -m 755 -o 0 -g 0 -d $(ROOT)/usr/bin/
 	install -m 755 -o 0 -g 0 irkerd $(ROOT)/usr/bin/irkerd
@@ -48,5 +53,5 @@ irker-$(VERS).tar.gz: $(SOURCES) irkerd.8 irkerhook.1
 
 dist: irker-$(VERS).tar.gz
 
-release: irker-$(VERS).tar.gz irkerd.html irkerhook.html
+release: irker-$(VERS).tar.gz irkerd.html irkerhook.html security.html hacking.html
 	shipper -u -m -t; make clean

security.txt

@@ -157,7 +157,7 @@ near resource limits.  An ordinary DoS attack would then be prevented
 from completely blocking all message traffic; the cost would be a
 whole lot of join/leave spam due to connection churn.
 
-= Authentication/Integrity =
+== Authentication/Integrity ==
 
 One way to help prevent DoS attacks would be in-band authentication -
 requiring irkerd submitters to present a credential along with each