I'm getting a weird error when I try to sFTP on a CentOS box (which I don't have root access).
when I run:
sftp -oPort=990 user@host.domain.com
I get the following error, which I suspect is a result of not being in "passive mode" (which works when I use Filezilla on Windows)
Connecting to host.domain.com ssh_exchange_identification: Connection closed by remote host Couldn't read packet: Connection reset by peer
Any suggestions?
On Tue, 2007-08-14 at 23:07 -0700, Rogelio Bastardo wrote:
I'm getting a weird error when I try to sFTP on a CentOS box (which I don't have root access).
Are you trying to use SFTP or FTPS? They're 2 completely different protocols. SFTP piggybacks on top of SSH, and FTPS is FTP over SSL.
Rogelio Bastardo wrote:
I'm getting a weird error when I try to sFTP on a CentOS box (which I don't have root access).
when I run:
sftp -oPort=990 user@host.domain.com mailto:user@host.domain.com
I get the following error, which I suspect is a result of not being in "passive mode" (which works when I use Filezilla on Windows)
Connecting to host.domain.com http://host.domain.com ssh_exchange_identification: Connection closed by remote host Couldn't read packet: Connection reset by peer
Any suggestions?
passive vs active or port mode is strictly a old school FTP thing, it has nothing to do with sftp which is part of the ssh protocol.
are you running a ssh server on port 990? it normally runs on port 22.
On 8/14/07, John R Pierce pierce@hogranch.com wrote:
passive vs active or port mode is strictly a old school FTP thing, it has nothing to do with sftp which is part of the ssh protocol.
are you running a ssh server on port 990? it normally runs on port 22.
My problem actually turns out to be I need to use FTPS instead of SFTP (hence the ssh errors).
Unfortunately, I don't have root access to the box where I need this, so I'm not quite sure how I'll get that tool, unless I "make install" it or grab a binary somewhere (I can't seem to find source code for FTPS while googling).
I hear that LFTP also would do what I need to do with FTP over SSL (implicit encryption).
Rogelio Bastardo wrote:
On 8/14/07, *John R Pierce* <pierce@hogranch.com mailto:pierce@hogranch.com > wrote:
passive vs active or port mode is strictly a old school FTP thing, it has nothing to do with sftp which is part of the ssh protocol. are you running a ssh server on port 990? it normally runs on port 22.
My problem actually turns out to be I need to use FTPS instead of SFTP (hence the ssh errors).
'ftps' is kind of an orphan, I don't believe there's actually any sort of RFC or spec for it. pretty much everything I've seen uses sftp/scp/ssh instead
'ftps' is kind of an orphan, I don't believe there's actually any sort of RFC or spec for it. pretty much everything I've seen uses sftp/scp/ssh instead
Forgive me, but i simply don't understand that statement. Both SFTP and FTPS are very much alive and well in the real world. Each has it's strengths depending on implementation requirements. Not everyone wants users to have shell access, regardless of how controlled that shell may be.
For the owner of this thread: Yes. LFTP is the command line client you want to use for FTPS. For the Linux GUI, look at Filezilla. There are several Windows clients available.