GNU bug report logs - #74832
guix copy incorrectly assumes port is 22

Previous Next

Package: guix;

Reported by: Dariqq <dariqq <at> posteo.net>

Date: Thu, 12 Dec 2024 16:46:02 UTC

Severity: normal

Tags: patch

Merged with 33266

Full log


Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Dariqq <dariqq <at> posteo.net>
To: bug-guix <at> gnu.org
Subject: guix copy incorrectly assumes port is 22
Date: Thu, 12 Dec 2024 16:45:20 +0000
Hello,

Here is bug report number 3 with guile-ssh <at> 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 <at> 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 <at> 0.17 :
#<session dariqq <at> domain:10022 (disconnected) 7f21d88a2fe0>

with-guile-ssh <at> 0.18:
#<session dariqq <at> 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?




This bug report was last modified 176 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.