From: Bryan Turner <bturner@atlassian.com>
To: Kevin Kendzia <kevin.kendzia@googlemail.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Issues with newest version of openssh 8.8p1-1
Date: Tue, 28 Sep 2021 00:32:05 -0700 [thread overview]
Message-ID: <CAGyf7-FBgmRTmjKFjMi2p5MArGEQh9a4Z6RA6FO-2U4D5jGnmA@mail.gmail.com> (raw)
In-Reply-To: <CAKcQ8=cyq46=eF8NZtUifmfHgWUphmHPYh4s3oQrHjiX2nqEmQ@mail.gmail.com>
On Mon, Sep 27, 2021 at 11:40 PM Kevin Kendzia
<kevin.kendzia@googlemail.com> wrote:
>
> Updated to openssh (8.8p1-1) and git didn't get the keys anymore.
> Couldn't pull or push. After reverting back to 8.7p1-2 it works as
> intended.
>
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.
>
> What did you do before the bug happened? (Steps to reproduce your issue)
> Updated system packages (openssh)
> What did you expect to happen? (Expected behavior)
> Can git pull without issues
> What happened instead? (Actual behavior)
> Permission Denied due to key error
> What's different between what you expected and what actually happened?
> I couldn't push pull whatever because the keys haven't been recognized somehow
> Anything else you want to add:
> I reverted from openssh 8.8p1-1 to 8.7p1-2 to make it work again
> Please review the rest of the bug report below.
> You can delete any lines you don't wish to share.
Ultimately this isn't a Git issue; it's an SSH issue. My guess would
be that upgrading to OpenSSH 8.8 picks up the change to stop using RSA
signatures using SHA-1 hashes by default.[1]
You can update your ~/.ssh/config to add these lines to revert that
and allow using those keys again:
Host old-host
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
With that said, though, if possible a better solution is to generate
new SSH keys using ECDSA, Ed25519 or another stronger signature and
switch to those.
Hope this helps!
Bryan
[1] https://www.openssh.com/releasenotes.html
next prev parent reply other threads:[~2021-09-28 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 6:40 Issues with newest version of openssh 8.8p1-1 Kevin Kendzia
2021-09-28 7:32 ` Bryan Turner [this message]
2021-09-29 22:58 ` brian m. carlson
2021-09-28 7:45 ` Carlo Arenas
2021-09-28 7:54 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGyf7-FBgmRTmjKFjMi2p5MArGEQh9a4Z6RA6FO-2U4D5jGnmA@mail.gmail.com \
--to=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=kevin.kendzia@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).