🚀 go-pugleaf

Kris, 

The "problem" is that Adobe chose to use an outdated, insecure protocol as the primary method of communication with their product.   

Outdated as of when? Seems to me its still the standard protocol used. You say "most serious security managers are requiring sftp and blocking ftp": as of when exactly? I don't remember anyone telling me I couldn't use FTP in the last two years either within a WAN environment or an ISP. 

 *That does not mean I am not sympathetic to your wish to see secure FTP implemented in GoLive.* 

It does mean I don't understand either the vehemence of your original contribution or the idea you seem to wish to put across that Adobe has somehow chosen not implement something which is somehow "standard" already with everyone else as of I don't know when. 

Can you help with stats on how many FTP servers actually serving clients out there in the real world already support secure FTP as opposed to not and who actually reject standard FTP traffic? 

chose to use an outdated, insecure protocol as the primary method of communication with their product   

Are we doing something unusual? Has every other FTP server and client out there supported secure FTP for years without me noticing? Its always possible I guess. Seems to me that secure FTP support even in standalone FTP clients is of relatively recent origin. 

Make the feature request! The more momentum behind it the more chance it has. You seem to want this badly, yet sending an e-mail to an engineering team is too much bother? If you send one, I'll send two. 

Thanks for the caps restraint. It makes life so much easier (really) ;-) 

John