Skip to content

Commit 7d821ab

Browse files
Merge pull request #78 from ISISComputingGroup/keeper_ssh
Keeper ssh
2 parents 21a6fb1 + 8a434fe commit 7d821ab

File tree

1 file changed

+26
-3
lines changed

1 file changed

+26
-3
lines changed

doc/tools/SSH-keys.md

Lines changed: 26 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,30 @@ example, by being copied onto instruments). Do not share your **private** key. T
3030
is additionally encrypted using your selected password.
3131
:::
3232

33-
## Setting up SSH agent
33+
{#keeper_ssh}
34+
## Keeper
35+
36+
To avoid having to copy and paste your passphrase every time, you can use [Keeper](https://ukri.sharepoint.com/sites/thesource/SitePages/Keeper-Password-Manager.aspx) to store your passwords and SSH keys.
37+
38+
If you want to use Keeper (you'll need the desktop client for this, _not_ the browser plugin) for storing your SSH keys, and not have local plain text copies on your machine, you can do so.
39+
40+
This is done by following [this guide](https://docs.keeper.io/en/keeperpam/privileged-access-manager/ssh-agent#activating-the-ssh-agent) with your public key, private key and passphrase filled in.
41+
42+
You may need to [turn the `OpenSSH` agent off](https://docs.keeper.io/en/keeperpam/privileged-access-manager/ssh-agent#windows-note-on-ssh-agent-conflicts) if it's on your machine - see if `ssh-agent` is running in your services in task manager.
43+
44+
It would also be a good idea to change the vault timeout to something relatively short to minimise scope of access for when the SSH keys are available.
45+
46+
### SSH works and prompts to use passphrase, but git doesn't show the prompt
47+
If `ssh [email protected]` works fine, your SSH key has been added to Github and `ssh` is using it.
48+
49+
You may need to set the `GIT_SSH` environment variable to wherever your ssh executable is, as git might try and use its own ssh executable which doesn't seem to work with Keeper. `where ssh` will tell you where this is.
50+
51+
{#manual_ssh_agent}
52+
## Manually Setting up SSH agent
53+
54+
```{note}
55+
Ignore this section if you followed {ref}`the section on setting up keeper as your ssh agent<keeper_ssh>`.
56+
```
3457

3558
In a powershell window, run the following commands:
3659
```powershell
@@ -59,7 +82,7 @@ To connect via SSH to an instrument, use:
5982
ssh spudulike@NDXINST
6083
```
6184

62-
This will prompt you on each connection for the passphrase to unlock your SSH key, this is the
85+
(If you aren't [using Keeper](#keeper_ssh)) This will prompt you on each connection for the passphrase to unlock your SSH key, this is the
6386
password you set earlier for your personal SSH key. You will not be prompted for an
6487
account password; your key is sufficient to grant you access.
6588

@@ -72,7 +95,7 @@ run a command as a privileged user.
7295
:::
7396

7497
Typing the password to unlock your SSH key for each instrument would be tedious.
75-
To avoid this, we can **temporarily** add the key to the SSH agent:
98+
To avoid this, we can either [use Keeper](#keeper_ssh), or **temporarily** add the key to the SSH agent:
7699

77100
```
78101
ssh-add

0 commit comments

Comments
 (0)