From f35dfec2090fc47fe53a27cec1c213d8ad9ecaea Mon Sep 17 00:00:00 2001
From: Ivan Chinenov <hjvt@hjvt.dev>
Date: Tue, 14 Oct 2025 03:52:42 +0300
Subject: [PATCH] doc: mention chowning knot binary
Change-Id: oyttstwvptztlwkptwxovxvuoxqvyzuo

---
 docs/knot-hosting.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/knot-hosting.md b/docs/knot-hosting.md
index ee3f635c..9567da34 100644
--- a/docs/knot-hosting.md
+++ b/docs/knot-hosting.md
@@ -39,10 +39,11 @@ go build -o knot ./cmd/knot
 ```
 
 Next, move the `knot` binary to a location owned by `root` --
-`/usr/local/bin/knot` is a good choice:
+`/usr/local/bin/` is a good choice. Make sure the binary itself is also owned by `root`:
 
 ```
 sudo mv knot /usr/local/bin/knot
+sudo chown root:root /usr/local/bin/knot
 ```
 
 This is necessary because SSH `AuthorizedKeysCommand` requires [really
-- 
2.39.5