From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: OpenSSH_9.2p1 sftp prompt now "s " instead of "sftp> "
Date: Wed, 8 Feb 2023 16:37:02 +0100 [thread overview]
Message-ID: <Y+PBnngWZnBeBLmD@calimero.vinschen.de> (raw)
In-Reply-To: <Y+N1m/6dE22a7H2C@calimero.vinschen.de>
On Feb 8 11:12, Corinna Vinschen via Cygwin wrote:
> On Feb 8 07:59, Thomas Wolff via Cygwin wrote:
> >
> >
> > Am 08.02.2023 um 03:17 schrieb Brian Inglis via Cygwin:
> > > On 2023-02-07 15:22, Voris, Ben via Cygwin wrote:
> > > > For example:
> > > > : sftp user@127.0.0.1
> > > > Connected to 127.0.0.1.
> > > > s bye
> > > > : type sftp
> > > > sftp is hashed (/usr/bin/sftp)
> > > > : ssh -V
> > > > OpenSSH_9.2p1, OpenSSL 1.1.1s 1 Nov 2022
> > > > On Linux with a much older ssh:
> > > > : ssh -V
> > > > OpenSSH_8.2p1 Ubuntu-4ubuntu0.5, OpenSSL 1.1.1f 31 Mar 2020
> > > > : sftp user@127.0.0.1
> > > > Connected to 127.0.0.1.
> > > > sftp> bye
> > > > Windows 10 21H2. This occurs both using Mintty and Windows Terminal.
> > > > For what I do, the only issue is the prompt.
> > >
> > > ++
> > >
> > Yes, it sends s^[[7G^D, which is really weird.
>
> Looks like this occurs in libedit. Downgrading to the former
> version of libedit "fixes" the problem.
You may want to try the new libedit release 2021030-4. Thanks to
Christoph Reiter from the MSYS2 community for pointing out a patch.
Corinna
prev parent reply other threads:[~2023-02-08 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 22:22 Voris, Ben
2023-02-08 2:17 ` Brian Inglis
2023-02-08 6:59 ` Thomas Wolff
2023-02-08 10:12 ` Corinna Vinschen
2023-02-08 15:37 ` Corinna Vinschen [this message]
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=Y+PBnngWZnBeBLmD@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/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).