From a3b733aa156831abd6fa7b19572c3f80c2ba6c31 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?F=C3=A9lix=20Pi=C3=A9dallu?= Date: Sun, 26 May 2024 13:31:39 +0200 Subject: [PATCH] cleanup messages --- doc/DESCRIPTION.md | 2 +- doc/POST_INSTALL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/DESCRIPTION.md b/doc/DESCRIPTION.md index 071e154..5045c92 100644 --- a/doc/DESCRIPTION.md +++ b/doc/DESCRIPTION.md @@ -57,7 +57,7 @@ At the end of the installation, the app displays the public_key and the user to You should now authorize the public key for user `servera` on server B by logging into server B with user `servera` and running: ``` -mkdir ~/.ssh -p 2>/dev/null +mkdir ~/.ssh -p touch ~/.ssh/authorized_keys chmod u=rw,go= ~/.ssh/authorized_keys cat << EOPKEY >> ~/.ssh/authorized_keys diff --git a/doc/POST_INSTALL.md b/doc/POST_INSTALL.md index d08142e..f984977 100644 --- a/doc/POST_INSTALL.md +++ b/doc/POST_INSTALL.md @@ -5,7 +5,7 @@ __PUBLIC_KEY__ Do so by running those commands on __SERVER__ with user __SSH_USER__: ``` -mkdir ~/.ssh 2>/dev/null +mkdir ~/.ssh -p touch ~/.ssh/authorized_keys chmod u=rw,go= ~/.ssh/authorized_keys echo "__PUBLIC_KEY__" >> ~/.ssh/authorized_keys