Setup SSH Keys
To be able to gain remote access to the Skynet.
$USERNAME Refers to your Skynet username, for example I would replace $USERNAME with silver
Windows
If you are using Windows then you should use PowerShell, not cmd.
Prep
First we set up the ssh folder and create a skynet folder within it for neatness
Create Key
Now we will create the ssh key itself.
<comment>: this is a comment to yerself about what the key is for- I often use
username@host,silver@skynet.
- I often use
- Location:
./$USERNAME, your skynet username../silverfor example.
- Password: Press Enter twice for no password on the key.
If you are creating this key for a CI/CD pipeline (user_deploy*) then adding a password will cause it to fail.
It will create two files: $USERNAME and $USERNAME.pub inside ~/.ssh/skynet
Linux Only
Openssh will complain if the keys permissions are too permissive.
To fix this use
Create Config
Above we created a folder for Skynet keys.
Ye can do the same with Gitlab/Github/... in the future.
The only downside is that we now have to tell ssh what key to use in what situation.
Back up to the .ssh folder.
Now we have to create the config file.
Notice how it has no extension.
Windows
Open it up in any text editor available to you.Linux
You can edit it from command line using nano Or open up in a text editor.Windows/Linux
This is what we want to have in the file.
The below is valid currently and suitable for users and admins.
Host *.skynet.ie 193.1.99.* 193.1.96.165
User $USERNAME
IdentityFile ~/.ssh/skynet/$USERNAME
IdentitiesOnly yes
Add key to account
Go to the modify SSH page and paste in the contents of $USERNAME.pub.
You will now be able to SSH into Skynet like so: