From f67f064e67bfb014dc91c167bd2ae0a53bf2b017 Mon Sep 17 00:00:00 2001
From: TomRicci <44097104+TomRicci@users.noreply.github.com>
Date: Mon, 21 Oct 2024 09:10:58 +0200
Subject: [PATCH] fix: message scpdownload scpupload in selfAddPersonalAccess

---
 bin/plugin/restricted/selfAddPersonalAccess | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/bin/plugin/restricted/selfAddPersonalAccess b/bin/plugin/restricted/selfAddPersonalAccess
index 89babda..506cbd0 100755
--- a/bin/plugin/restricted/selfAddPersonalAccess
+++ b/bin/plugin/restricted/selfAddPersonalAccess
@@ -45,10 +45,10 @@ Usage: --osh SCRIPT_NAME --host HOST --user USER --port PORT [OPTIONS]
                               must not specify --user in that case. However, for this protocol to be usable under a given
                               remote user, access to the USER@HOST:PORT tuple must also be allowed.
                               PROTO must be one of:
-                              scpup    allow SCP upload, you--bastion-->server
-                              scpdown  allow SCP download, you<--bastion--server
-                              sftp     allow usage of the SFTP subsystem, through the bastion
-                              rsync    allow usage of rsync, through the bastion
+                              scpupload    allow SCP upload, you--bastion-->server
+                              scpdownload  allow SCP download, you<--bastion--server
+                              sftp         allow usage of the SFTP subsystem, through the bastion
+                              rsync        allow usage of rsync, through the bastion
   --force                  Add the access without checking that the public SSH key is properly installed remotely
   --force-key FINGERPRINT  Only use the key with the specified fingerprint to connect to the server (cf selfListEgressKeys)
   --force-password HASH    Only use the password with the specified hash to connect to the server (cf selfListPasswords)