Here we go again! 2FA vs Gitlab instructions.
marco.antoniotti at unimib.it
Sun Mar 27 16:09:02 UTC 2022
thanks for the help.
No. I am not using PuTTY as terminal on W11.
I was able to upload the new key to Gitlab, but it still does not work.
Pageant seems to be running, and Sourcetree gives me a very suspicious
git -c diff.mnemonicprefix=false -c core.quotepath=false
--no-optional-locks push -v --tags --set-upstream origin master:master
Pushing to common-lisp.net:mantoniotti/cl-plot.git
*Server refused public-key signature despite accepting key!*
FATAL ERROR: Network error: Software caused connection abort
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I am at a loss. This should not be so difficult.
On Sun, Mar 27, 2022 at 5:16 PM Jon Boone <ipmonger at delamancha.org> wrote:
> Hi Marco!
> I know this can all be very frustrating, but hang in there!
> The two public keys you have from pageant are in PEM (aka base64)
> format. That format is no longer accepted by Github/Gitlab, which require
> the RFC4716 format instead.
> I am wondering if you are using PuTTY as your terminal client on Windows
> 11. If so, you might find this particular section of documentation for
> working with PuTTY from Oracle to be helpful:
> In particular, by exporting the key from the PPK format PuTTY uses to the
> OpenSSH format, you can then import the OpenSSH format into both GitHub and
> — jb
> On Mar 27, 2022, 10:41 -0400, Marco Antoniotti <marco.antoniotti at unimib.it>,
> Oh well. I have a ssh-agent running. I am using Git Bash on a W11 machine.
> $ ssh-add
> Could not open a connection to your authentication agent.
> BTW. I am also trying to get SourceTree to work. I have Pageant running
> with my keys loaded.
> I noticed that I do not have my most recent public key loaded on Gitlab
> (but it has two old ones that *shoould* still work). But the site does not
> understand (and *I do not fuc*ing understand*) the format in which the
> key should be pasted in there.
> I generated the key with Pageant and the file contains what you see in the
> I apologize for the tone, but I really really believe that both Github and
> Gitlab have gone way off on a tangent with all of this. Especially because
> they have not gone back to git to improve the messaging.
> All the best
> On Sun, Mar 27, 2022 at 4:22 PM Jon Boone <ipmonger at delamancha.org> wrote:
>> 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
>> — jb
>> On Mar 27, 2022, 10:20 -0400, Marco Antoniotti <
>> marco.antoniotti at unimib.it>, wrote:
>> 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.gitgit 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 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
> 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
Marco Antoniotti, Professor tel. +39 - 02 64 48
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...
More information about the clo-devel