From be6c16d74c53ea3d1a10a4b0586db8eb9af19c6e Mon Sep 17 00:00:00 2001
From: Gmer4Lfe <gmer4lfe@gmail.com>
Date: Sat, 4 Jul 2026 01:03:29 -0400
Subject: [PATCH] =?UTF-8?q?Fix=20Gitea=20SSH=20probe=20in=20plugin=20insta?=
 =?UTF-8?q?ller=20=E2=80=94=20drop=20bogus=20'info'=20command?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The probe ran 'ssh git@$ip info' expecting Gitea's banner in the response,
but 'info' is a Gitolite convention Gitea doesn't implement — it returns
'error: Too few arguments' instead, which never matched the grep, so a
real reachable Gitea host was never detected. Confirmed on HOST2: connecting
with no trailing command returns Gitea's actual banner correctly.
---
 Plugin/varaverk.plg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Plugin/varaverk.plg b/Plugin/varaverk.plg
index 541cc5f..a0712ca 100644
--- a/Plugin/varaverk.plg
+++ b/Plugin/varaverk.plg
@@ -145,7 +145,7 @@ if [[ ! -d "$SCRIPTS_DIR/.git" ]]; then
         while IFS= read -r peer_ip; do
             if ssh -i "$GITEA_SSH_KEY" -p "$SSH_PORT" \
                    -o ConnectTimeout=3 -o StrictHostKeyChecking=no \
-                   -o BatchMode=yes "git@${peer_ip}" info 2>/dev/null | grep -q "varaverk\|Gitea\|gitea"; then
+                   -o BatchMode=yes "git@${peer_ip}" 2>/dev/null | grep -q "varaverk\|Gitea\|gitea"; then
                 GITEA_IP="$peer_ip"
                 log "Gitea found on Tailscale peer $GITEA_IP"
                 break