unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "dabbede@gmail.com" <dabbede@gmail.com>
To: Davide Gandolfi <dabbede@gmail.com>,
	Felix Lechner <felix.lechner@lease-up.com>,
	help-guix@gnu.org
Subject: Re: Connection refused to Guix-hosted SSH
Date: Wed, 19 Oct 2022 21:39:03 +0200	[thread overview]
Message-ID: <CAEwYQ4T+TtWYmdG7ycCjgsvu6cTdDktr8WREg10E9AuT_pdC1w@mail.gmail.com> (raw)
In-Reply-To: <Y1BH0FtSGp5Qm6C4@3900XT>

Hi Efraim,

Il mer 19 ott 2022, 20:54 Efraim Flashner <efraim@flashner.co.il> ha
scritto:

> From a previous email it looks like you only have an rsa key
>

Good point. At the beginning of the discussion I was recycling an old key,
and when I saw those messages (I was not sure whether errors or just info)
I also tried generating a new pair, but I could not connect either.
Moreover, in my configuration I was allowing for password authentication,
so I guess that at least that option should still be valid, even with a non
valid key-pair.

[...]


> There was recently a change in openssh to deprecate support for rsa-sha1
> keys. Try generating new ssh keys using a newish version of openssh and
> using that as your keys for pcp or test, and see if that works for
> connecting using a key.
>

>
>
[...]

Now unfortunately I can not reproduce, because I reinstalled a new system.
Now it works flawlessly.

Thank you, regards

   Davide

  reply	other threads:[~2022-10-19 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12 20:22 Connection refused to Guix-hosted SSH dabbede
2022-10-13  5:30 ` Oleg Pykhalov
2022-10-14  8:27   ` dabbede
2022-10-13 21:04 ` Felix Lechner via
2022-10-14  8:54   ` dabbede
2022-10-14 17:06     ` Felix Lechner via
2022-10-14 20:01       ` dabbede
2022-10-14 20:18         ` Felix Lechner via
2022-10-19 18:54         ` Efraim Flashner
2022-10-19 19:39           ` dabbede [this message]
2022-10-15  6:01     ` Oleg Pykhalov
2022-10-16  7:53       ` dabbede

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=CAEwYQ4T+TtWYmdG7ycCjgsvu6cTdDktr8WREg10E9AuT_pdC1w@mail.gmail.com \
    --to=dabbede@gmail.com \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).