Switch to full style
Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

FTP to FTPS Proxy Upload (does wingate support this)

Jul 04 14 8:47 am

We're considering adding a WinGate server to our current infrastructure and are quite impressed by its features. We have a fairly obscure scenario used by our corporation and are wondering if this could be achieved using WinGate?

ServerA sends ftp traffic to "ftp://destionationC.com" which goes to proxy server "WingateB"

WingateB establishes an "ftps"(not sftp) session to the DestinationC.com server and sends all traffic from ServerA to it.

Re: FTP to FTPS Proxy Upload (does wingate support this)

Jul 04 14 12:02 pm

Hi

is this "implicit" ftps? E.g. no negotiation, just connect on a different port with SSL first then do FTP over it?

Currently WinGate could probably do this with the control connection, but not the data connection - we'd need to add support for that.

do you have a specific client / server you're testing with? We could probably add this fairly easily. Negotiated FTPS would be a bit more work though.

Re: FTP to FTPS Proxy Upload (does wingate support this)

Jul 04 14 12:33 pm

Hi

I had another look through the code. Looks like there are some issues relating to piping through to another server with ssl that we should fix anyway.

Is this a reverse proxy scenario? Does the behaviour need to alter based on where the client is connecting?

Does ServerA know it's talking to a proxy, or does it think WinGate is the FTP server?

Currently the reverse proxy function is only triggered by the USER command, which may not be the first command (and nowadays commonly isn't, e.g. FEAT or AUTH commands are replacing USER as the first command).

Regards

Adrien

Re: FTP to FTPS Proxy Upload (does wingate support this)

Jul 09 14 10:26 am

Sorry for the delay, 3-day weekend and came back to a busy desk.

We use both implicit & explicit negotiation. SeverA does know its talking to a proxy server.

We currently have tlswrapper implemented that handles both options. http://www.tlswrap.com/

This program produces complications of its own and we would love to have more options/alternatives for us in future.
Post a reply