From: Dariqq <dariqq@posteo.net>
To: 74832@debbugs.gnu.org
Subject: bug#74832: guix copy incorrectly assumes port is 22
Date: Thu, 12 Dec 2024 16:45:20 +0000 [thread overview]
Message-ID: <bd64a6c0-3a38-4fe2-9315-c4ff6be02e91@posteo.net> (raw)
Hello,
Here is bug report number 3 with guile-ssh@0.18.
When using a host defined in ~/.ssh/config in the --to/--from argument
in guix-copy "send-to-remote-host" and "retrieve-from-remote-host"
incorrectly pass the port as 22 to open-ssh-session.
This then leads to a failure when trying to connect:
--8<---------------cut here---------------start------------->8---
guix copy hello --to=name
guix copy: error: failed to authenticate server at 'domain': not-known
--8<---------------cut here---------------end--------------->8---
With guile-ssh@0.17 guile-ssh silently ignored the "wrong port" and
instead connects to the one specified by the ssh Host
--8<---------------cut here---------------start------------->8---
guix copy hello --to=name
with guile-ssh@0.17 :
#<session dariqq@domain:10022 (disconnected) 7f21d88a2fe0>
with-guile-ssh@0.18:
#<session dariqq@localhost:22 (disconnected) 7f17887a2fe0>
--8<---------------cut here---------------end--------------->8---
Are the (or port 22) clauses in guix/scripts/copy.scm still neccesary?
From my limited testing removing them fixed the problem and passing a
port of #f will result in 22 being used.
This might also be a problem in other places wghere open-ssh-session is
used?
next reply other threads:[~2024-12-12 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 16:45 Dariqq [this message]
2024-12-12 17:35 ` bug#74832: guix copy incorrectly assumes port is 22 Tomas Volf
2024-12-12 19:31 ` bug#74832: [PATCH] guix: Do not default to 22 ssh port (let guile-ssh do it) Tomas Volf
2024-12-19 2:33 ` bug#74832: guix copy incorrectly assumes port is 22 Maxim Cournoyer
2024-12-19 9:30 ` Tomas Volf
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=bd64a6c0-3a38-4fe2-9315-c4ff6be02e91@posteo.net \
--to=dariqq@posteo.net \
--cc=74832@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.