Topic: Secure FTP

[Thomas V.]

First off I’d like to thank everyone that make the free download/usage of e-smith possible!

I have a small suggestion. - How about a Public Secure FTP Access option?

I’m on a local network with 200-300 (season depended) other fellow IT students. This kind of environment sees a lot of network sniffers. As a result I have closed my FTP. But with a SFTP there would be no problem. I have previously used SFTP on a FreeBSD with great success. But the time and knowledge it takes to maintain a system of this kind, to keep unwanted guests out is far beyond what I can muster. So the SME is a heaven send solution. But FTP Access is my primary reason for keeping a server running. And I REALLY miss that option.

Thomas.

[robert]

SME already includes a secure ftp server. This is a subserver of the ssh server.
Go to the remote access panel in the server-manager and enable ssh access. You now have an sftp server waiting for connections.
For windows clients, the free for non-commercial use ssh client available from www.ssh.com comes with an sftp client.
For mac clients, the author of MacSSH has written a commercial, but inexpensive, sftp client called MacSFTP.
For Unixes, the most common client is called simply sftp and is included in openssh-clients.

[Thomas V.]

Thanks!

Things work great now.

Now why didn’t I figure that out myself  
Have fun!
Thomas.

[Harris]

Is that SFTP server listening on port 21 or what?

[zoikz]

>Author: Harris (jannis_AT_home.nl)
>Date:   01-03-03 09:30

>Is that SFTP server listening on port 21 or what?
no its listening on the default ssh port (22) but you'll still need an sftp client (normal ftp clients can't understand the encryption) which will use port 22 by default

[David Yip]

Dear all:

Is it possible to change the starting directory for the SFTP Client like FTP?


David Yip

[David Yip]

Dear All:

I mean that change the user's root directory in Server side for SFTP.

Thanks

[Mike]

Hi everyone

Have got a problem trying to get an sftp connection.
I get the following:
*************************************************************************
Finding Host www.mydomain.com ...
Connecting to 111.222.333.444:22
Connected to 111.222.333.444:22, Waiting for Server Response
Server Welcome: SSH-1.99-OpenSSH_3.1p1
Client Version: SSH-2.0-WS_FTP-7.6-2002.08.23
Signature Verified
Session Keys Created
Ciphers Created
New Client->Server ciphers in place.
New Server->Client ciphers in place.
Completed SSH Key Exchange. New Keys in place.
User Authenticated OK!
Completed SSH User Authentication.
Started subsystem "sftp" on channel e9d8868f
Received channel request "exit-status" status(1), for channel e9d8868f
Received channel close/eof(0x60) message for channel e9d8868f
Error 842c0000 receiving sftp packet
error 842c0000 initializing sftp protocol
Sending channel close message for channel e9d8868f
SSH Transport closed.
*************************************************************************
SSH authentication seems to be O.K. but then sftp is starting on a subsystem.
If I read this right then my E-smith box apperently sends an exit command.
Have never worked with sftp but would like to shield my passwords from showing up on sniffers.

Some of you guys have any idea's?