From 7245c5ccf30cabe29c99e40d17cd1f01482f5e67 Mon Sep 17 00:00:00 2001 From: "Philip Sargent (muscogee)" Date: Tue, 7 Jan 2020 20:55:21 +0000 Subject: [PATCH 01/17] Adding how to upload keys yourself for your second machine --- handbook/computing/keyexchange.html | 41 ++++++++++++++++++++++++++--- 1 file changed, 38 insertions(+), 3 deletions(-) diff --git a/handbook/computing/keyexchange.html b/handbook/computing/keyexchange.html index b5143d083..12f39f8d3 100644 --- a/handbook/computing/keyexchange.html +++ b/handbook/computing/keyexchange.html @@ -43,13 +43,48 @@
  • Erm, dunno...please fill in

    • Android

    - -
  • Erm, dunno...please fill in
    • - +

    iOS

    + +
  • Erm, dunno...please fill in
    • +

    Your second machine

    +

    OK, you have an uploaded and usable key and you can ssh into the expo server. Now you want to set up a key for another machine such as your phone. You don't need a nerd admin now, you can do this yorself. +

      +
    1. On your new machine, generate a key-pair. Since you are probably using a different operating system on your second machine, read the instructions above for the relevant OS. Yes you will be generating a new key. Do not re-use the key you had already. +
    2. This time though, you will want to be sure that the key has a meaningful label. On Linux this means something like this: + ssh-keygen -C "anathema.device@crowley" +(if your name is Anathema Device and your new machine is "crowley"). Just click through the questions it asks accepting the defaults. It will tell you what the key files are called and where it has put them. +
    3. +If you accepted the defaults, the public key will be called id_rsa.pub and it will be in ~/.ssh/ - check that this is the case. +
    4. Now copy the public key file to your first machine, the one that is already set up with a working key exchange with the expo server. Using email to yourself is easiest. +
    5. Rename the public key file to something that won't be confused with anyone else's key file, to e.g. anathema-id_rsa.pub +
    6. Now upload the public key using sFTP to expo.survex.com/home/expo/.ssh/keys/ +
    7. Now login to the expo server on your first machine and do these commands: +$ ssh expo@expo.survex.com +
      expo@expo:~$ cd .ssh +
      expo@expo:~/.ssh$ cat keys/anathema-id_rsa.pub >>authorized_keys +
      expo@expo:~/.ssh$ ./list-keys.sh +
      expo@expo:~/.ssh$ cat list-of-key-owners +       +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:
      +anathema.device@crowley +
    8. 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. +

      +

      Note that by using sFTP like this we avoid having to use a text editor over ssh. If you know what you are doing you can do this of course, but the above process is less likely to cause problems for a Windows user setting up their phone as a second device where they are not experienced with vi or nano. + + + +