From: cappy <cappycdn@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh/sftp oddness
Date: Mon, 29 Aug 2005 09:34:04 -0400 [thread overview]
Message-ID: <47f70463050829063467c3a1e8@mail.gmail.com> (raw)
In-Reply-To: <4310EDB1.6010408@edoceo.com>
On 27/08/05, David Busby <busby@edoceo.com> wrote:
> List,
> When I use this Windows based SSH tool to connect to my new dev box with sftp it get's two dialogs about 'enter auth
> response' as if the sftp-subsystem is spitting out extra control characters. That's not a real big issue but what is
> that jEdit on Win or Lin cannot connect, it says authentication failure, but the logs on the dev box show that the jEdit
> was authenticated, odd. Where would it be spitting out these extras? How can I fix this? Has anyone else seen it?
>
> /djb
> --
> gentoo-user@gentoo.org mailing list
>
I had a similar problem and I fixed it by updating both Putty and
WinSCP. Hopefully those are the programs you are using in your
windows environment.
As far as what was the reall issue I did not probe further.
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-08-29 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 22:48 [gentoo-user] ssh/sftp oddness David Busby
2005-08-29 13:34 ` cappy [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=47f70463050829063467c3a1e8@mail.gmail.com \
--to=cappycdn@gmail.com \
--cc=gentoo-user@lists.gentoo.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