Here we go again! 2FA vs Gitlab instructions.

Jon Boone ipmonger at delamancha.org
Sun Mar 27 14:22:26 UTC 2022


If you’re using a bash/zsh environment, use ‘ssh-add’ to load your private keys into the ssh agent before you interact with the remote repository.

— jb
On Mar 27, 2022, 10:20 -0400, Marco Antoniotti <marco.antoniotti at unimib.it>, wrote:
> Hi
>
> I am trying to import a repo in Gitlab.  I just created the repo using the web interface (CL-PLOT).
> This is what the instructions on the site say.
>
> cd existing_repo
> git remote rename origin old-origin
> git remote add origin git at common-lisp.net:mantoniotti/cl-plot.git
> git push -u origin --all
> git push -u origin --tags
>
> Once I try git push I get the dreaded message.
>
> $ git push -u origin --all
> git at common-lisp.net: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> Why?  I.e., why doesn't git understand the 2FA I set up a long time ago?  Why I cannot get my SSH keys to work?  How can I change the remote spec in order not to have to go through this every other month?
>
> Thank you
>
> All the best
>
> Marco
>
>
>
> --
> Marco Antoniotti, Professor                           tel. +39 - 02 64 48 79 01
> DISCo, Università Milano Bicocca U14 2043   http://dcb.disco.unimib.it
> Viale Sarca 336
> I-20126 Milan (MI) ITALY
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/clo-devel/attachments/20220327/eb105edb/attachment.html>


More information about the clo-devel mailing list