Secure FTP

[ronks]

I access sonic.net for file transfer via "ftp.sonic.net" without any prefix for sftp:// or ftps://
as I do with other providers. Is this insecure; and if it is, what is the workaround? (Haven't had any problems, just want to be sure.)

[thulsa_doom]

FTP is wide open and unencrypted so, depending on your security needs (like maybe not transmitting your password over untrusted infrastructure in clear text), it is not secure at all.

I recommend enabling shell access (our support staff can do this for you over the phone) and using SCP through the host shell.sonic.net.

[ronks]

Thanks! Is the shell-access route compatible with FTP utilities like Filezilla?

[mkutner]

Yes. In Filezilla, enter host name

sftp://shell.sonic.net

[ronks]

Sounds good; thanks! I'll try that.

[ankh]

Nice! secure access works with Mac Cyberduck

[ankh]

P.S. -- before I got to this topic, I'd tried the straight FTP connection from terminal.

Got this popup:
Verify Certificate
A failure occurred during certification trust verification ...
The certificate for this server has expired. You might be
connected to a server that is pretending to be "ftp.sonic.net" ...
...
ftp.sonic.net Issued by: Comodo Class 3 Security Services CA
Expired: Monday, June 4, 2007 at 4:59:59 PM Pacific Daylight Time

----
Well, no, I didn't trust that. Found this "Secure FTP" topic instead.

Thank you.