[tahoe-lafs-trac-stream] [Tahoe-LAFS] #4098: CircleCI is Broken

[Tahoe-LAFS]

#4098: CircleCI is Broken
-------------------------+-----------------------
     Reporter:  meejah   |      Owner:
         Type:  task     |     Status:  new
     Priority:  normal   |  Milestone:  undecided
    Component:  unknown  |    Version:  n/a
   Resolution:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------------

Comment (by sajith):

 Replying to [comment:7 hacklschorsch]:

 > I didn't find anything regarding HTTPS for checkout, but I stumbled over
 https://batsov.com/articles/2022/09/20/resetting-circleci-checkout-ssh-
 keys/ saying:

 The error message Bozhidar Batsov describes does not have the "checkout
 key has zero length" message, so perhaps they were solving a different
 thing?

 In any case, in app.circleci.com, under tahoe-lafs project settings -> ssh
 keys, there are three things:

 - Deploy key (repo-specific SSH key, for !GitHub access)
 - User key (user-specific SSH key, for !GitHub access)
 - Additional ssh keys

 Under "Additional SSH Keys", there's a fingerprint of
 "SHA256:v1Kg79rxSj0qyLEb27BeBQqPQ8B2qxTwy2K2kqOeJE4" (configured to use
 with the hostname github.com), which I guess is that of an ssh key someone
 (exarkun maybe?) added.  That seems to be the only thing I am able to
 delete.

 But "Additional SSH Keys" are about "keys to the build VMs that you need
 to deploy to your machines", not checkouts.  I don't know what one would
 deploy to github.com from CircleCI.  Will I break something (I don't know
 what that something would be) if I delete that key?

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4098#comment:9>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage