Your message dated Sat, 27 Jul 2024 10:01:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#964953: lftp: set sftp:auto-confirm yes doesn't work
has caused the Debian Bug report #964953,
regarding lftp: set sftp:auto-confirm yes doesn't work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
964953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964953
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lftp
Version: 4.8.4-2+b1
Severity: normal
Dear Maintainer,
In Debian Testing (Bullseye) lftp option "set sftp:auto-confirm yes" stopped
working. The problem is that ssh doesn't output the prompt "Are you sure you
want to continue connecting (yes/no)?" and so lftp can't answer it.
lftp :~> set sftp:auto-confirm yes
lftp :~> set log:enabled true
lftp :~> open sftp://example.com -u someuser,somepassword
lftp [email protected]:~> ls
---- Running connect program (ssh -a -x -s -l someuser example.com sftp)
---> sending a packet, length=5, type=1(INIT), id=0
The authenticity of host 'example.com (1.2.3.4)' can't be established.
<--- ECDSA key fingerprint is
SHA256:bugmuoMea8sptvHgg8uyo2dQN857geiLloXWRj3sC4g.
`ls' at 0 [Connecting...]
(hangs forever)
There is no problem on Debian Stable (Buster).
Workaround is to run "ssh -a -x -s -l someuser example.com sftp" (which shows
the prompt) and to accept the key manually.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.7.0-1-amd64 (SMP w/24 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lftp depends on:
ii libc6 2.30-8
ii libgcc-s1 [libgcc1] 10.1.0-4
ii libgnutls30 3.6.14-2
ii libidn2-0 2.3.0-1
ii libreadline8 8.0-4
ii libstdc++6 10.1.0-4
ii libtinfo6 6.2-1
ii netbase 6.1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages lftp recommends:
ii openssh-client [ssh-client] 1:8.3p1-1
lftp suggests no packages.
-- debconf-show failed
--- End Message ---
--- Begin Message ---
fixed 964953 4.9.2-1
thanks
Hello Martin,
Am Montag, dem 13.07.2020 um 12:22 +0200 schrieb Martin Ždila:
> In Debian Testing (Bullseye) lftp option "set sftp:auto-confirm yes"
> stopped
> working. The problem is that ssh doesn't output the prompt "Are you
> sure you
> want to continue connecting (yes/no)?" and so lftp can't answer it.
>
> lftp :~> set sftp:auto-confirm yes
> lftp :~> set log:enabled true
> lftp :~> open sftp://example.com -u someuser,somepassword
> lftp [email protected]:~> ls
> ---- Running connect program (ssh -a -x -s -l someuser example.com
> sftp)
> ---> sending a packet, length=5, type=1(INIT), id=0
> The authenticity of host 'example.com (1.2.3.4)' can't be
> established.
> <--- ECDSA key fingerprint is
> SHA256:bugmuoMea8sptvHgg8uyo2dQN857geiLloXWRj3sC4g.
> `ls' at 0 [Connecting...]
>
> (hangs forever)
I tested with the 4.9.2 version (stable and above) and looks like the
option auto-confirm works (server anonymized):
lftp ~> open sftp://example.com -u user,password
lftp [email protected]:~> ls
---- Starte Verbindungsprogramm (ssh -a -x -s -l user example.com sftp)
---> sending a packet, length=5, type=1(INIT), id=0
The authenticity of host 'example.com (X.X.X.X)' can't be established.
<--- RSA key fingerprint is
SHA256:AOvcGrr+x496rN7GeKZUIBJdyhaCcWc8SoL0wBcHoR8.
<--- This key is not known by any other names.
<--- Are you sure you want to continue connecting
(yes/no/[fingerprint])? yes
<---
<--- Warning: Permanently added 'example.com' (RSA) to the list of
known hosts.
<--- Received disconnect from X.X.X.X port 22:2: Too many
authentication failures
<--- Disconnected from X.X.X.X port 22
If it is still a problem please tell us.
Thank you for reporting.
--
Noël Köthe <noel debian.org>
Debian GNU/Linux, www.debian.org
signature.asc
Description: This is a digitally signed message part
--- End Message ---
