From: "Frederickson, Jonathan" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "70034@debbugs.gnu.org" <70034@debbugs.gnu.org>
Subject: bug#70034: Hostkey error when pulling or building from private git repository
Date: Fri, 12 Apr 2024 14:50:43 +0000 [thread overview]
Message-ID: <3664e546721f49f4c1c74be198989b9479945037.camel@akamai.com> (raw)
In-Reply-To: <1156672208.1243481.1711555774538.JavaMail.zimbra@universite-paris-saclay.fr>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
It looks like this is https://github.com/libgit2/libgit2/issues/6612
And one of the comments on that issue from the libgit2 maintainer made
me realize there's a workaround. Using github.com as an example since
the initial report was having trouble with a channel on github, if you
run this:
$ ssh-keyscan github.com >> ~/.ssh/known_hosts
...it seems to fix the issue, because ssh-keyscan fetches host keys of
all types from the remote host, rather than just one (as seems to
happen when you connect to a remote host via SSH normally).
Obviously would prefer a proper fix, but this is a relatively low-
impact workaround for now.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4655 bytes --]
prev parent reply other threads:[~2024-04-15 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 16:09 bug#70034: Hostkey error when pulling or building from private git repository Atte Torri via Bug reports for GNU Guix
2024-04-10 10:14 ` Tim Johann
2024-04-11 17:34 ` Frederickson, Jonathan via Bug reports for GNU Guix
2024-04-12 14:50 ` Frederickson, Jonathan via Bug reports for GNU Guix [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3664e546721f49f4c1c74be198989b9479945037.camel@akamai.com \
--to=bug-guix@gnu.org \
--cc=70034@debbugs.gnu.org \
--cc=jfrederi@akamai.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).