Singdall wrote:
FTP is to hazardous to mess with for most companies and for things that might need to be secured a better way would be to setup a https site for directory browsing. then the large files could be downloaded via the web page under https requiring some kind of validation.
i still think that working off of a 56k and using the above application is a bad idea no matter how you transfer the data. 56k is the killer in this thread.
FTP = dangerous
http = not as bad, but not secure
https = best of both worlds and is SECUREABLE unlike http or FTP.
Yeah. Depends on the size of the company and the quality of their security IT staff. FTP is as secure as the network it's on and the authentication methodology you use.
https is only "more secure" because it has a built in secure authentication process. Out of the box, it's more secure then FTP. If your guys know what they're doing, there's fundamentally zero difference.
The danger you can get into is thinking that by tossing a server with https secured pages on it, you've "secured" your remote access. You've in many cases opened yourself up to just as many methods of attack as any other remote accessable system. At the end of the day, anything that can be accessed across a network is vulnerable, and only as secure as the weakest point in the whole system. What application you're using has very little to do with it...