Re: ssh Problem using it for SFTP
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, Jan 13, 2016 at 07:13:57PM -0500, Steve Matzura wrote:
> I hope this isn't off-topic by too much. If it is, a word to me
> privately and I'll wait for responses to queries I've made elsewhere.
>
> I maintain two FTP servers and support four Windows-based FTP clients
> for users of those servers--FTP Voyager, FlashFXP, Filezilla, and
> WinSCP. One server accepts all four clients, the other accepts all but
> FTP Voyager, indicating a configuration difference.
>
> I've asked about this on the comp.security.ssh Usenet newsgroup, but
> Usenet being what it is, I might have to wait at least a week before
> getting a response of any kind, and my Voyager users are starting to
> get restless for an answer as to what I did to break access for
> them--i.e., they'd rather fight than switch.
>
> Here are the two sshd_configs without comments, greatly shortening
> what you'll be looking at.
I'm not as much of an SSH guru to "get" what's going on by just reading
configs, but as a hint: there is an "-d" option to sshd which starts
it in debug mode. If you then chose a non-standard port (i.e. 2022 or
whatever seems suitable), then you can follow, on the terminal what's
going on, like so:
sshd -d -p 2022
If you add more "-d" (up to three), verbosity increases.
regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlaXXfAACgkQBcgs9XrR2kabawCeOG0jJz31azT07FYqTn5fdy2Q
2EoAnjBr+V3hdioveJljEmB6bNfKtNHA
=fY6r
-----END PGP SIGNATURE-----
Reply to: