From 297b0b310237282befe12c98b949441042bf6bcc Mon Sep 17 00:00:00 2001 From: Valentin Brandl Date: Sun, 15 Jul 2018 22:54:08 +0200 Subject: [PATCH] Fix formatting --- content/post/bind9-api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/post/bind9-api.md b/content/post/bind9-api.md index 755e470..b5e0997 100644 --- a/content/post/bind9-api.md +++ b/content/post/bind9-api.md @@ -70,9 +70,9 @@ API but this still does not protect against replay attacks. If an attacker managed to intercept an request to the API, (s)he would be able to resend the same request to the server and re-execute the command. To prevent this, the API server has to be placed behind a -reverse proxy like [nginx][11] to encrypt the requests using TLS or as I am -doing it, make the server listen on a private IP address inside an -encrypted VLAN ([tinc][1] in my case). +reverse proxy like [nginx][11] to encrypt the requests using TLS or as +I am doing it, make the server listen on a private IP address inside +an encrypted VLAN ([tinc][1] in my case). Once the body was verified using the pre-shared secret `nsupdate` is invoked and the following update or delete scripts are passed via