The client, FileZilla, ignored the error on PROT P and continued on. Things go a little too fast to be noticed. I think it is not a bad idea to automatically use the same SSL configuration. I can't think of any thing where an API caller wants different SSL configurations for control and data connections. Can you?
Sai Pullabhotla Phone: (402) 408-5753 Fax: (402) 408-6861 www.jMethods.com On Fri, Dec 12, 2008 at 8:11 AM, Niklas Gustavsson <[email protected]> wrote: > On Fri, Dec 12, 2008 at 2:58 PM, Sai Pullabhotla > <[email protected]> wrote: >> Yes, I was programmatically setting up the FtpServer using the factory >> classes. I thought I got SSL connections working, but when I watched >> it closely, data was being sent in clear as I did not set >> SSLConfiguration on the data connection. Once, I set this up, >> everything worked as expected. > > Hmm, did the client swallow the error reply that PROT returned, or do > we have a bug where we don't send an error if SSL is not configured > for the data connection? > >> So, just to confirm, if I set up the server using the XML >> configuration, then I do not need to have a nested <ssl> element in >> the <data-connection>, right? > > Right. Maybe we should enable the same thing for the API? > > /niklas >
