FTP SSL in web browser

vikas027 · 12-21-2011, 06:33 AM

Dear All,

I am given a task to build a FTP (vsftpd) server on CentOS 5.7 64 Bit.

I have generate RSA key using this link.

Now, I am able to access the the VSFTPD server through a windows tool SmartFTP, but not allowing connections when trying to access the URL ftp://192.168.1.20. Ideally, I think it should ask me to save the certificate, but I am not geting any prompt to save the certificate.

I have tried on Mozilla Firefox and Google Chrome. My end users need to access the URL over browser.

Please help !

TB0ne · 12-21-2011, 09:09 AM

Quote:

Originally Posted by vikas027

Dear All,
I am given a task to build a FTP (vsftpd) server on CentOS 5.7 64 Bit. I have generate RSA key using this link.

Now, I am able to access the the VSFTPD server through a windows tool SmartFTP, but not allowing connections when trying to access the URL ftp://192.168.1.20. Ideally, I think it should ask me to save the certificate, but I am not geting any prompt to save the certificate. I have tried on Mozilla Firefox and Google Chrome. My end users need to access the URL over browser.

Ok...so you're wanting to use SSL with FTP? Then try putting in "ftps://192.168.1.20" into your browser...that's FTP with SSL. You can also try the filezilla plug-in for your browser as well.

anomie · 12-21-2011, 09:39 AM

@vikas027: Apologies in advance for going OT, but if there is any possibility for you to push back and suggest sftp instead to your customers, then do it. (If using a web browser is a requirement, then why not https?)

TB0ne · 12-21-2011, 09:48 AM

Quote:

Originally Posted by anomie

@vikas027: Apologies in advance for going OT, but if there is any possibility for you to push back and suggest sftp instead to your customers, then do it. (If using a web browser is a requirement, then why not https?)

I would agree with that as well. FTP is woefully insecure.

vikas027 · 12-21-2011, 02:08 PM

Quote:

Originally Posted by anomie

@vikas027: Apologies in advance for going OT, but if there is any possibility for you to push back and suggest sftp instead to your customers, then do it. (If using a web browser is a requirement, then why not https?)

I tried to convince them, but they are adamant about using FTP over SSL.

ftps://IP does not works.

However, I think till now I will try to use make them use SmartFTP only.

Many Thanks Anomie and TBone.

TB0ne · 12-21-2011, 03:20 PM

Quote:

Originally Posted by vikas027

I tried to convince them, but they are adamant about using FTP over SSL.

ftps://IP does not works.

Ok...how about telling us what error(s) you're getting??

Quote:

However, I think till now I will try to use make them use SmartFTP only.
Many Thanks Anomie and TBone.

Did you try Filezilla or FireFTP for Firefox?

vikas027 · 12-22-2011, 02:01 PM

Quote:

Originally Posted by TB0ne

Ok...how about telling us what error(s) you're getting??

Did you try Filezilla or FireFTP for Firefox?

I could not find any SSL option in FireFTP.

I am getting this error.

Quote:

"530 Non-anonymous sessions must use encryption"

TB0ne · 12-22-2011, 06:45 PM

Quote:

Originally Posted by vikas027

I could not find any SSL option in FireFTP.

I am getting this error.

Open the site with ftps://<address or server name>. In FireFTP, click EDIT->Connections. Set your certificate/authentication there. Read the FireFTP docs, or look at Google. FireFTP supports FTPS easily.

Again, FTP (even FTPS), is *NOT* that secure....SFTP is much more secure, easier to administer, and easier to script for. FTP and Telnet are 30-year old tech, and shouldn't be used, when there are better options.

vikas027 · 12-24-2011, 04:47 AM

Quote:

Originally Posted by TB0ne

Open the site with ftps://<address or server name>. In FireFTP, click EDIT->Connections. Set your certificate/authentication there. Read the FireFTP docs, or look at Google. FireFTP supports FTPS easily.

Thanks TB0ne, I will check this and revert.

Quote:

Originally Posted by TB0ne

Again, FTP (even FTPS), is *NOT* that secure....SFTP is much more secure, easier to administer, and easier to script for. FTP and Telnet are 30-year old tech, and shouldn't be used, when there are better options.

I understand, but customer is adamant to use native FTP.

Lately, they have told me that do not want to use even SSL now.