Skip to content

Conversation

@Tom-Willemsen
Copy link
Member

No description provided.

Copy link
Member

@GRyall GRyall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏😁

Comment on lines +27 to +29
For the avoidance of doubt, the **public** key (`*.pub`) can be freely shared with everyone (for
example, by being copied onto instruments). Do not share your **private** key. The private key
is additionally encrypted using your selected password.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

put this in a warning/caution admonitiion i'd say.

## Deploying the public key

- Add your public key to the [keys repository](https://github.com/ISISComputingGroup/keys).
- Ask a developer whose key is *already* deployed to run the deployment script, which will
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which deployment script? we have many.

Comment on lines 66 to 68
Firstly, if you intend to run a command across many instruments, it is worth getting that command
reviewed by another developer and running it together. This is **especially** true if you intend to
run a command as a privileged user.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

caution admonition

@rerpha rerpha merged commit 57d8f7c into master Aug 27, 2025
2 checks passed
@rerpha rerpha deleted the key_based_auth branch August 27, 2025 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants