() Bob Proulx <b...@proulx.com> () Sat, 4 Dec 2021 10:21:04 -0700 > How can i remedy this situation?
Did you just recently upgrade your system and that included the latest OpenSSH 8.8? If so then I think you have hit the SHA1 hash obsolescence problem. Thanks for the quick reply. I see on my system: $ ssh -V OpenSSH_8.4p1 Debian-5, OpenSSL 1.1.1k 25 Mar 2021 so i don't think that's the problem. The error message says "Too many authentication failures" which sounds to me like there is a count somewhere (state) that needs to be reset somehow. Anyway... https://savannah.gnu.org/maintenance/SshAccess/ I recommend using procedure number 2 listed there as that is the superior solution. But it requires a little more effort and so I didn't make it the first option. The first option is the least effort workaround to the problem. I will include the relevant part below so this message is self-contained. ... thanks for the pointer. Just to be future-proof, i have followed the procedures and created a proper ED25519 (i think), and registered it w/ savannah. FWIW: $ ssh-keygen -l -f ~/.ssh/.i/sv 256 SHA256:ES6Obfoua7ywmGX8kH6K3FGWGQB12lQOTxP+ZR6FO9M ttn@abolire (ED25519) I still see the same error on retry, unfortunately. And as an update on the new system status I have been working on it but there is a long list of things needed to be completely finished before it can be swapped into place without breaking other parts of the system. It's a large all-or-nothing problem. I am confident the task will be completed before the end of this month. https://savannah.gnu.org/maintenance/SavannahHosts/ Cool. I won't pester you further, then (this month :-D). Good luck and let me know if you need someone to do some light testing. -- Thien-Thi Nguyen
signature.asc
Description: PGP signature