Skip to content

Improve SSH key handling instructions #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 13, 2023
Merged

Improve SSH key handling instructions #108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions content/collections/create.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,9 +143,8 @@ For collections to be included in the Open Terms Archive organisation only. For
- Connect to the server with `ssh <username>@<host>` (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`.

Expand Down