Reports until 13:21, Tuesday 28 April 2026
H1 General
jeffrey.kissel@LIGO.ORG - posted 13:21, Tuesday 28 April 2026 (90034)
Generating an SHA Key and posting it to git.ligo.org so you can clone repos on a new laptop
J. Kissel, J. Freed

It's not the "right" place to find this information, but I was helping Josh get started with git, and I found my 2022 LHO:63463. We needed that step of generating an SSH key and posting it to his git.ligo.org profile. Of course, in 4 years, a minor detail has changed -- the location of where you put it on the web.

So, here's the 2026 version of the instructions on how to generate an SSH (SHA256) key and get ligo.org to recognize it enough to give you permissions to clone a project:

##ALL THE SAME
     jeffrey.kissel@opslogin0:/ligo/gitcommon/Calibration/ifo$ ssh-keygen 
     Generating public/private rsa key pair.
     Enter file in which to save the key (/ligo/home/jeffrey.kissel/.ssh/id_rsa): 
     /ligo/home/jeffrey.kissel/.ssh/id_rsa already exists.
     Overwrite (y/n)? y
     Enter passphrase (empty for no passphrase): 
     Enter same passphrase again: 
     Your identification has been saved in /ligo/home/jeffrey.kissel/.ssh/id_rsa.
     Your public key has been saved in /ligo/home/jeffrey.kissel/.ssh/id_rsa.pub.
     The key fingerprint is:
     SHA256:XQnWdPoBVmHwdsX3i+qpeTvANGQHFiI7zTXFN1oF7ew jeffrey.kissel@opslogin0
     The key's randomart image is:
     +---[RSA 2048]----+
     |     . . *B+=+O+.|
     |      = ++.=.@ .+|
     |     o oo . B B +|
     |      .  + o o =.|
     |        S o   + .|
     |         o   . E |
     |          . .    |
     |          .+.    |
     |         o++o    |
     +----[SHA256]-----+
     jeffrey.kissel@opslogin0:/ligo/gitcommon/Calibration/ifo$ cat /ligo/home/jeffrey.kissel/.ssh/id_rsa.pub 
     ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCebNagyBGRjYsoP4RT8KZ74HLONo6B4VOwBNUQpOPrNnMvQTD3NfTQJHWTgkcAFiCB2yLeioqJQmrigTd9BjnKx/1Eo4z1wvhC/hvCvD07IcvLgogP1lujyDyx7qYHBw46W1pFXXt1wqkFYFiDxcsNRgqhFqFBvdyVJdfPZs+GHqK8Df6AfKKZTWqrYgzpqYbvzl9q21E3vEUyTQamoftBimCZVSj1cz7+5W7giWBcBNmcuHzrV2/Af7pfzj8zoveXv/9qISyLKp0F4zlB52/lih9TzxTg36l8MCzIb2592xVsRaYtuxb8SA4Sst8bUqVvUFclj/rCD1ytEDfMvKyp jeffrey.kissel@opslogin0

###HERE'S WHERE IT'S DIFFERENT

Then I 
- went to https://git.ligo.org/-/user_settings/ssh_keys/ (####INSTEAD OF https://git.ligo.org/-/profile/keys)
- copied the above public id_rsa.pub hash into the "Key" field, 
- then let it auto-title the key,
- change the with expiration date something in the year 2080, and 
- hit the blue "add key" button.


Now, you can, say go to the https://git.ligo.org/spi/simulation/ page, and hit the blue "Code" button (####it's no longer called "Clone"), hit the two squares icon for copy in the "Clone with SSH" address, then in a (new or refreshed) terminal type

    $ git clone git@git.ligo.org:spi/simulation.git

and you're in business. 
From there, the CONTRIBUTING guide to pydarm is a place that I found the most helpful in how to develop / interact with a git project.