Re: Here we go again! 2FA vs Gitlab instructions.
Marco Antoniotti <[email protected]>
| Newsgroups | gmane.lisp.common-lisp-net.devel |
|---|---|
| Message-ID | <CAG0Nw2k3+8f60yjjs_feRhbZLZ+SdAHCTy-uZtmcNryPm+pwKA@mail.gmail.com> |
Hi I succeded. I had to reboot the machine. The new Sourcetree came up and I was able to add the new private key to Pageant, which was not correctly running before. Go figure. In any case, all of this should not be so difficult. Nothing that is at fault with the CLNET folks, but seriously! The Gitlab and Github people should get a grip. All the best Marco On Sun, Mar 27, 2022 at 6:31 PM Philipp Marek <[email protected]> wrote: > >*Server refused public-key signature despite accepting key!* > > https://www.openssh.com/txt/release-8.8 says > > > Potentially-incompatible changes ================================ This > release disables RSA signatures using the SHA-1 hash algorithm by default. > This change has been made as the SHA-1 hash algorithm is cryptographically > broken, and it is possible to create chosen-prefix hash collisions for > <USD$50K [1] > ... > Incompatibility is more likely when connecting to older SSH > implementations that have not been upgraded or have not closely tracked > improvements in the SSH protocol. > > > Can you update your SSH client to a newer Version? > -- 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