unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 54950@debbugs.gnu.org
Subject: bug#54950: Connecting to remote guix daemon with encrypted SSH key fails
Date: Wed, 08 Jun 2022 16:30:28 -0400	[thread overview]
Message-ID: <87a6amkie3.fsf@gmail.com> (raw)
In-Reply-To: <87pmli1u3e.fsf@systemreboot.net> (Arun Isaac's message of "Fri,  15 Apr 2022 16:39:25 +0530")

Hi,

Arun Isaac <arunisaac@systemreboot.net> writes:

> I have an SSH key encrypted with a passphrase. When I try connecting to
> a remote guix daemon with that encrypted SSH key, it fails with the
> following error message.
>
> $ GUIX_DAEMON_SOCKET=ssh://foo guix build -v3 hello
> guix build: error: SSH authentication failed for 'foo': Access
> denied for 'publickey'. Authentication that can continue: publickey
>
> I expected some kind of prompt asking me for the passphrase, but did not
> get any. The same command works if I set up ssh-agent and add the
> relevant key to it.

I suspect this is due to changes in OpenSSH *client* that now refuse
older RSA keys for security reasons.

Could you retry with the following option: 'StrictHostKeyChecking no'
applied to the host in your ~/.ssh/config?

If that's indeed the problem, you'll want to upgrade your key to
something more modern like ed25519.

I hope that helps,

Maxim




  reply	other threads:[~2022-06-08 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-15 11:09 bug#54950: Connecting to remote guix daemon with encrypted SSH key fails Arun Isaac
2022-06-08 20:30 ` Maxim Cournoyer [this message]
2022-06-15  6:30   ` Arun Isaac
2022-06-15 15:46     ` Maxim Cournoyer
2022-06-16  6:34       ` Arun Isaac
2022-06-16 14:01         ` Maxim Cournoyer
2022-06-17  6:52           ` Arun Isaac

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=87a6amkie3.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=54950@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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).