From 8b8abf6658ce74440ca7e24c29602692a58ac2c9 Mon Sep 17 00:00:00 2001 From: Matti Schneider Date: Wed, 13 Dec 2023 17:27:51 +0100 Subject: [PATCH] Improve SSH key handling instructions --- content/collections/create.en.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/collections/create.en.md b/content/collections/create.en.md index f3d357aa..f8a50f62 100644 --- a/content/collections/create.en.md +++ b/content/collections/create.en.md @@ -143,9 +143,8 @@ For collections to be included in the Open Terms Archive organisation only. For - Connect to the server with `ssh @` (usual usernames: `debian`, `ubuntu`…) - Create a new SSH key: `ssh-keygen -q -N "" -f ~/.ssh/ota-deploy` - Add the public key to `authorized_keys`: `cat ~/.ssh/ota-deploy.pub >> ~/.ssh/authorized_keys` - - Copy the public key with `cat ~/.ssh/ota-deploy.pub` and keep it temporarily for the next steps - Add the private key to the SSH authentication agent: `ssh-add ~/.ssh/ota-deploy` (start the SSH agent before if necessary with `eval ${ssh-agent -s}`) - - Copy the private key with `cat ~/.ssh/ota-deploy` and keep it temporarily for the next steps +- Copy the public and private keys and back them up in the shared passwords repository Note: user must have the right to `sudo`.