Gitlab situation 2025-02-26
: Martin Holmes
Minutes: 45
After some discussion with RT:
- The current gitlab instance doesn’t support cloning by ssh, which means that although you can set up ssh keys in the gitlab interface, they’re no use because you have to clone over https.
- That means that either you’re challenged to input user name and password every time you push to the repo, or you devolve to a potentially insecure approach which stores your netlink credentials in clear text in your git profile.
- We could opt to have the system moved (where?) to a location where SSH is allowed. That would take about a day and a half.
- We could also set up authentication tokens to remove some of the inconvenience, but neither I nor Robert seem to have done that before, and it doesn’t seem as secure and convenient as SSH keys anyway.
Now discussing this with GN.