expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-13 09:27:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixing <br> to <br /> for <!DOCTYPE html>

Browse Source
This commit is contained in:
Philip Sargent
2020-03-05 23:19:47 +00:00
parent db1050315d
commit 73f1693ffb
5 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
handbook/computing/keyexchange.html
View File

@@ -74,16 +74,16 @@
If you accepted the defaults, the public key will be called <span style="font-family:monospace; size=x-small; background-color: lightgray">id_rsa.pub</span> and it will be in <span style="font-family:monospace; size=x-small; background-color: lightgray">~/.ssh/</span> - check that this is the case.
<li>Now copy the public key file to your <em>first machine</em>, the one that is already set up with a working key-pair setup with the expo server. Using email to yourself is easiest.
<li>Now upload the public key using sFTP (Filezilla configured to use sFTP, which uses Pageant by default) to <span style="font-family:monospace; size=x-small; background-color: lightgray">expo.survex.com/home/expo/.ssh/keys/</span>
<li>Now login to the expo server on your first machine and do these commands:<br>
<li>Now login to the expo server on your first machine and do these commands:<br />
Be <b>extremely careful</b> to type ">>" and not ">" in the fourth line below otherwise you will delete <i>everyone's</i> logins.
<tt><font color=red">$</font> ssh expo@expo.survex.com
<br><font color=blue">expo@expo:~$</font> cd .ssh
<br><font color=blue">expo@expo:~$</font> cp -p authorized_keys authorized_keys.backup
<br><font color=blue">expo@expo:~/.ssh$</font> cat keys/id_rsa.pub >>authorized_keys
<br><font color=blue">expo@expo:~/.ssh$</font> ./list-keys.sh
<br><font color=blue">expo@expo:~/.ssh$</font> cat list-of-key-owners
<br /><font color=blue">expo@expo:~$</font> cd .ssh
<br /><font color=blue">expo@expo:~$</font> cp -p authorized_keys authorized_keys.backup
<br /><font color=blue">expo@expo:~/.ssh$</font> cat keys/id_rsa.pub >>authorized_keys
<br /><font color=blue">expo@expo:~/.ssh$</font> ./list-keys.sh
<br /><font color=blue">expo@expo:~/.ssh$</font> cat list-of-key-owners
</tt>
This adds your key on to the end of the authorized keys list, runs a little script to extract the names of all the people who have added keys (24 keys as of Jan.2020) and prints out the list. You should see that the last line says:<br>
This adds your key on to the end of the authorized keys list, runs a little script to extract the names of all the people who have added keys (24 keys as of Jan.2020) and prints out the list. You should see that the last line says:<br />
<span style="font-family:monospace; size=x-small; background-color: lightgray">anathema.device@crowley</span>
<li>Now your public key is installed for your second machine. You check that it works by logging into the expo server using ssh from your second machine.
</p>