-
Couldn't load subscription status.
- Fork 2
Document key-based auth #67
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.
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
Conversation
8057e7c to
8a2108d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏😁
| 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. |
There was a problem hiding this comment.
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.
doc/tools/SSH-keys.md
Outdated
| ## 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 |
There was a problem hiding this comment.
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.
doc/tools/SSH-keys.md
Outdated
| 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
caution admonition
No description provided.