Code ReviewSign In / operations / debs / wmf-sre-laptop / 221df3d340ef11b19db310775bb19e037fa87294 / . / docs / wmf-laptop-sre / SETUP.ssh
blob: 66c4f2dd1a11710d70aab7478eb172c4f27dcb9a [file] [log] [blame]
This describes the setup using disk-based key store:
- Create two separate SSH keys for "production" and "cloud":
ssh-keygen -t ed25519
and store them in two separate files (e.g. ~/.ssh/id_wmf_prod and ~/.ssh/id_wmf_cloud)
- Run update-ssh-config. It will patch your ssh config file, and start the two SSH agent
services via systemd.
- Before using the SSH keys you need to load the keys into the SSH agents, unfortunately
it's a bit hacky as ssh-add doesn't allow to specify the auth socket via an option, so
best to add a small script which does:
export SSH_AUTH_SOCK​=​/run/​user​/​1000​/​ssh​-​wmf​-​prod​.​socket
ssh-add .ssh/id_wmf_prod
export SSH_AUTH_SOCK​=​/run/​user​/​1000​/​ssh​-​wmf​-​cloud​.​socket
ssh-add .ssh/id_wmf_cloud
- Finally we need to populate the known hosts file. First create the following directory:
mkdir ~/.ssh/known_hosts.d
We have a script which needs the known host information from To initially
seed the data, you need to temporarily disable SSH host checking.
ssh -o StrictHostKeyChecking​=​ask
Compare the presented host fingerprint against
https​:​// If it matches,
then type 'yes'.
Then the same for restricted​.​bastion​.​wmflabs​.​org
Then run "wmf-update-known-hosts-production"​, it will fetch all host keys from bast2002.
It needs to re-run whenever new hosts are added, either do it manually when you can't log into
a host or setup a systemd timer (or cron).
You should now be able to login into Cloud VPS and production hosts.
Powered by Gitiles