From cf1826dc713b91516c91ddf00719e606ba82e26c Mon Sep 17 00:00:00 2001
From: Owen Jones <owen.jones@uwe.ac.uk>
Date: Tue, 8 Oct 2024 11:55:38 +0000
Subject: [PATCH] more keyfile location notes

---
 README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 69926d0..c8c6f22 100644
--- a/README.md
+++ b/README.md
@@ -7,10 +7,11 @@ Current WIP to quickly setup an SSH connection to the server, using `az ssh conf
 If an SSH config exists (it'll be created when they first setup a connection through vscode), open it up and check:
 * User is their full UWE email address (including host portion), spelt correctly, all in lowercase
 * Host is `csctcloud.uwe.ac.uk` (spelt correctly)
-* IdentityFile either correctly points to directory on H:\ drive, or on personal machines to C:\Users\X, /Users/X, or /home/X, or is omitted (so default key file used)
+* IdentityFile either correctly points to `H:\.ssh\id_rsa`, or on personal machines to `C:\Users\X\.ssh\id_rsa`, `/Users/X/.ssh/id_rsa`, or `/home/X/.ssh/id_rsa` (or another properly created keyfile if they've chosen a non-default location), or is omitted (so default keyfile used)
 
 If this is all correct/they haven't got to setting up vscode yet:
-* Look in .ssh folder (check this matches what is in SSH config) and check both public and private key are present
+* Look in their `.ssh` folder (check this matches what is in SSH config) and check both public and private key are present
+* If they don't have a `.ssh` folder - get them to go back to 'Generating a key' section of guide and go from there
 * Open up public key in notepad and check not malformed or accidentally overwritten
 
 Get them to connect to the server using Azure CLI (`az login`):
-- 
GitLab